-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Update Microsoft.Sql ARM API with "format: arm-id" where appropriate and x-ms-secret where appropriate #22292
Conversation
Hi, @matthchr Thanks for your PR. I am workflow bot for review process. Here are some small tips. Any feedback about review process or workflow bot, pls contact swagger and tools team. vscswagger@microsoft.com |
Swagger Generation Artifacts
|
Generated ApiView
|
Hi @matthchr, one or multiple breaking change(s) is detected in your PR. Please check out the breaking change(s), and provide business justification in the PR comment and @ PR assignee why you must have these change(s), and how external customer impact can be mitigated. Please ensure to follow breaking change policy to request breaking change review and approval before proceeding swagger PR review. |
Hi @matthchr, Your PR has some issues. Please fix the CI sequentially by following the order of
|
@ericshape can you review this? |
Note that the breaking change tool incorrectly classifies |
I investigated the ModelValidation failures and they are either:
|
1952004
to
443669c
Compare
@raych1 - can you confirm that the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
after @raych1 answer the question from the author, we could merge it to main branch.
Interesting. Why do we meet this spelling error issue? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you fix spell check errors?
If a property is annotated as |
@ericshape , I saw you approved this PR but still want to confirm with you will these chagnes be overridden next time when swagger is re-generates? |
I have updated this PR and fixed the x-ms-secret model validation errors (fixed the samples). The other model validation errors and spelling errors I believe are unrelated to this PR. |
@ericshape I will send a second PR targeting the new preview version once it merges and this PR is merged. Do you have any objection to this merging now? |
@matthchr , please fix |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
1023 - TypeFormatChanged are expected
the spellCheck error could be fixed by rebase/sync with latest main branch |
94e32bf
to
40deb8c
Compare
I rebased which in theory should fix the spellcheck errors |
…ere appropriate and x-ms-secret where appropriate (#2800) Create to sync Azure/azure-rest-api-specs#22292 [ReCreate this PR](https://github.com/azure-resource-manager-schemas/compare/main...azure-sdk:sdkAuto/sql?expand=1)
…and x-ms-secret where appropriate (Azure#22292) * Azure SQL ARM ID annotations * Fix secret annotations * Fix samples
ARM API Information (Control Plane)
Changelog
Add a changelog entry for this PR by answering the following questions:
Contribution checklist (MS Employees Only):
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Otherwise your PR may be subject to ARM review requirements. Complete the following:
Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review. Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.
Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.
If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.