-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
[Compute] New API Version 2021-08-01 #17118
Conversation
* Add supportedCapabilities in SnapshotUpdateProperties model * Add an example for update acceleratedNetwork on snapshots * Fix example model * clean up
* DiskRP swagger changes for TVM and CVM of version 2021-08-01 * adding examples for CVM * fix errors * fix errors * fix unreferences example file * fix for: additional properties not allowed error * fix spell check error * fix spell check for secureVMDiskEncryptionSetId property * fix prettier check * addressing comment * addressing comments
* RRP changes * Fix prettier
Hi, @haagha 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. vsswagger@microsoft.com |
[Call for Action] To better understand Azure service dev/test scenario, and support Azure service developer better on Swagger and REST API related tests in early phase, please help to fill in with this survey https://aka.ms/SurveyForEarlyPhase. It will take 5 to 10 minutes. If you already complete survey, please neglect this comment. Thanks. |
Swagger pipeline restarted successfully, please wait for status update in this comment. |
Hi, @haagha your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). |
Hi @haagha, Your PR has some issues. Please fix the CI sequentially by following the order of
|
ARM recommends string enums over boolean. Generally enums make better properties than booleans. They are more descriptive, flexible and future-proof while being easier for customers to discover, understand and use. Ref: https://armwiki.azurewebsites.net/rp_onboarding/process/api_review_best_practices.html?q=boolean#common-issues-found-in-review. In this case, you could do something more like this: "getSecureVMGuestState": [ None, SAS ]. Refers to: specification/compute/resource-manager/Microsoft.Compute/stable/2021-08-01/disk.json:3033 in 5dd4670. [](commit_id = 5dd4670, deletion_comment = False) |
@haagha, your first commit in the new PR already has edits (version changed to 2021-11-01). When adding a new API version, please carefully follow the process for constructing your PR. This is really important to help streamline the workload for ARM reviewers and handle your PR in as timely a manner as possible. The first commit should be the files from the current API version, unmodified. Changes (including updating the version) should go into subsequent commits. All of that notwithstanding, to avoid another round trip, I manually diffed your PR update against the most recent API version of the disk.json file checked into the public repo. Since the changes are modest and straightforward, I'll complete the review on the current PR. |
Note, this suggestion doesn't block ARM signoff, but you should consider making a change like this. |
@mentat9 We will make note of this for future releases, but IF Possible I would like to move forward with the current boolean type because the team wants to do a private preview soon, and making this change would require re-deployment of API and ARM manifest that could cause quite long delays. Thanks. |
@ArcturusZhang Are these new linting rules resulting in linting errors? Is this PR ready to be merged? |
The linter errors can be ignored. |
@ArcturusZhang the breaking changes are from a previous PR #16099 And ARM has signed off so I believe we can merge. Here is the SDK PR Azure/azure-sdk-for-net#25436 |
* new folder and files added for diskRP 2021-08-01 * Adding Location header to LRO responses examples * Add supportedCapabilities in SnapshotUpdateProperties model (Azure#16768) * Add supportedCapabilities in SnapshotUpdateProperties model * Add an example for update acceleratedNetwork on snapshots * Fix example model * clean up * DiskRP swagger changes for TVM and CVM of version 2021-08-01 (Azure#16671) * DiskRP swagger changes for TVM and CVM of version 2021-08-01 * adding examples for CVM * fix errors * fix errors * fix unreferences example file * fix for: additional properties not allowed error * fix spell check error * fix spell check for secureVMDiskEncryptionSetId property * fix prettier check * addressing comment * addressing comments * DiskRP Swagger changes for Remote Restore Point scenarios (Azure#16636) * RRP changes * Fix prettier * including communityGallery.json in package * suppress bodytoplevelproperties Co-authored-by: Theodore Chang <thchan@microsoft.com> Co-authored-by: LU WU <laurawu19@gmail.com> Co-authored-by: anshulsolanki21 <73930854+anshulsolanki21@users.noreply.github.com> Co-authored-by: sukodava <78733210+sukodava@users.noreply.github.com>
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Changelog
Add a changelog entry for this PR by answering the following questions:
Contribution checklist:
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 label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.
-[x] 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.
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 any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.