Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jack tn/test convert prettier #3024

Closed
wants to merge 18 commits into from
Closed

Jack tn/test convert prettier #3024

wants to merge 18 commits into from

Conversation

JackTn
Copy link

@JackTn JackTn commented Sep 18, 2023

ARM (Control Plane) API Specification Update Pull Request

PR review workflow diagram

Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

diagram

[1] ARM review queue (for merge queues, see [4])
The PRs are processed by time opened, ascending. Your PR may show up on 2nd or later page.
If you addressed Step 1 from the diagram and your PR is not showing up in the queue, ensure the label ARMChangesRequested
is removed from your PR. This should cause the label WaitForARMFeedback to be added.
[2] https://aka.ms/azsdk/support/specreview-channel
[3] List of SDK breaking changes approvers in pinned Teams announcement
[4] public repo merge queue, private repo merge queue (for ARM review queue, [1])

If you need further help with anything, see Getting help section below.

Purpose of this PR

What's the purpose of this PR? Check all that apply. This is mandatory!

  • New API version. (Such PR should have been generated with OpenAPI Hub, per this wiki doc.)
  • Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
  • Update existing version to fix swagger quality issues in S360.
  • Other, please clarify:
    • edit this with your clarification

Due diligence checklist

To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

Breaking changes review (Step 1)

  • If the automation determines you have breaking changes, i.e. Step 1 from the diagram applies to you,
    you must follow the breaking changes process.
    IMPORTANT This applies even if:
    • The tool fails while it shouldn't, e.g. due to runtime exception, or incorrect detection of breaking changes.
    • You believe there is no need for you to request breaking change approval, for any reason.
      Such claims must be reviewed, and the process is the same.

ARM API changes review (Step 2)

  • If this PR is in purview of ARM review then automation will add the ARMReview label.
  • If you want to force ARM review, add the label yourself.
  • Proceed according to the diagram at the top of this comment.

Viewing API changes

For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures

If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.

Getting help

@openapi-pipeline-app-test
Copy link

openapi-pipeline-app-test bot commented Sep 18, 2023

Next Steps to merge

Next steps that must be taken to merge this PR:
  • ❌ Your PR is in purview of ARM review (label: ARMReview). Please ensure your PR is on the ARM PR review queue - see instructions in steps 1 and 2 in the PR description diagram.
  • ❌ The required check named Automated merging requirements met has failed. This is the final check that must pass. Refer to the check in the PR's 'Checks' tab for details on how to fix it. In addition, refer to step 4 in the PR workflow diagram (even if your PR is for data plane, not ARM).

@openapi-pipeline-app-test
Copy link

openapi-pipeline-app-test bot commented Sep 18, 2023

Swagger Generation Artifacts

️️✔️~[NotRequired_Staging] ApiDocPreview succeeded [Detail] [Expand]
Posted by Swagger Pipeline | How to fix these errors?

@openapi-pipeline-app-test
Copy link

openapi-pipeline-app-test bot commented Sep 18, 2023

Swagger pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment.

@openapi-pipeline-app-test
Copy link

openapi-pipeline-app-test bot commented Sep 18, 2023

Swagger Validation Report

️️✔️BreakingChange succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️Breaking Change(Cross-Version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️LintDiff succeeded [Detail] [Expand]
Validation passes for LintDiff.
️️✔️~[NotRequired_Staging] Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
️️✔️SwaggerAPIView succeeded [Detail] [Expand]
️️✔️TypeSpecAPIView succeeded [Detail] [Expand]
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️️✔️PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️~[NotRequired_Staging] PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️~[NotRequired_Staging] SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️PR Summary succeeded [Detail] [Expand]
️️✔️Automated merging requirements met succeeded [Detail] [Expand]
Posted by Swagger Pipeline | How to fix these errors?

@JackTn
Copy link
Author

JackTn commented Sep 19, 2023

/azp run

@azure-pipelines
Copy link

No pipelines are associated with this pull request.

@JackTn
Copy link
Author

JackTn commented Sep 26, 2023

/azp run

@azure-pipelines
Copy link

No pipelines are associated with this pull request.

@JackTn
Copy link
Author

JackTn commented Oct 9, 2023

/azp run

@azure-pipelines
Copy link

Pull request contains merge conflicts.

@JackTn
Copy link
Author

JackTn commented Oct 9, 2023

/azp run

@azure-pipelines
Copy link

Pull request contains merge conflicts.

@JackTn
Copy link
Author

JackTn commented Oct 9, 2023

/azp run

@azure-pipelines
Copy link

Pull request contains merge conflicts.

@JackTn
Copy link
Author

JackTn commented Oct 9, 2023

/azp run

@azure-pipelines
Copy link

Pull request contains merge conflicts.

@JackTn
Copy link
Author

JackTn commented Oct 9, 2023

123

2 similar comments
@JackTn
Copy link
Author

JackTn commented Oct 9, 2023

123

@JackTn
Copy link
Author

JackTn commented Oct 9, 2023

123

@JackTn
Copy link
Author

JackTn commented Oct 9, 2023

/azp run

@azure-pipelines
Copy link

Pull request contains merge conflicts.

@JackTn
Copy link
Author

JackTn commented Oct 9, 2023

You don't have permission to trigger SDK Automation.
Please add yourself to Azure group from opensource portal if you are MSFT employee,
or please ask reviewer to add comment *** /openapibot sdkautomation ***.
Please ask [email protected] (or NullMDR in github) for additional help.

@JackTn
Copy link
Author

JackTn commented Oct 9, 2023

/azp run

@azure-pipelines
Copy link

No pipelines are associated with this pull request.

@JackTn
Copy link
Author

JackTn commented Oct 10, 2023

/azp run

@azure-pipelines
Copy link

No pipelines are associated with this pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants