[Microsoft.StorageSync] Fix S360 swagger linter errors reported for API version 2022-06-01#23412
Merged
MaryGao merged 2 commits intoAzure:mainfrom Apr 14, 2023
anpint:anpint-storagesync-linterfixes
Merged
[Microsoft.StorageSync] Fix S360 swagger linter errors reported for API version 2022-06-01#23412MaryGao merged 2 commits intoAzure:mainfrom anpint:anpint-storagesync-linterfixes
MaryGao merged 2 commits intoAzure:mainfrom
anpint:anpint-storagesync-linterfixes
Conversation
|
Hi, @anpint 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 |
ghost
added
the
Swagger Validation Report
|
Swagger Generation Artifacts
|
Generated ApiView
|
This was referenced Apr 3, 2023
ankushbindlish2
approved these changes
Apr 4, 2023
Member
ankushbindlish2
left a comment
ankushbindlish2
left a comment
There was a problem hiding this comment.
Would appreciate if you can share Afs pull request which enables Location header and have an effect to show linter error.
Member
Author
I don't think there was any change in the AFS service that caused the linter check to fail. Most likely it was added to S360 recently, and we were never really compliant to begin with. |
Member
|
@msyyc Could you help on Python breaking change? |
MaryGao
approved these changes
Apr 14, 2023
This was referenced Apr 14, 2023
JoshLove-msft
pushed a commit
to JoshLove-msft/azure-rest-api-specs
that referenced
this pull request
Apr 25, 2023
…PI version 2022-06-01 (Azure#23412) * Fix Location header in examples for pre/post backup and pre/post restore * Also fix location header in trigger change detection example
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo. If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:
N/A, fixing examples files
N/A, fixing examples files
N/A, fixing examples files
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.