Compute 2021 03 release #14223
Merged
Compute 2021 03 release #14223
Conversation
This file contains 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
|
Hi, @Sandido 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 started successfully, please wait for status update in this comment. |
ghost
added
the
|
Swagger pipeline started successfully, please wait for status update in this comment. |
* Deep deletion feature * Deep deletion cleanup * Deep deletion cleanup 2
Swagger Validation Report
|
Swagger Generation Artifacts
|
* Scheduled Events feature * Scheduled Events feature example
* PatchSetting assessment feature * PatchSetting assessment feature cleanup * Patchsetting example * Patchsetting example 2 * Patchsetting example 3 * Patchsetting example 4 * Patchsetting example 5
* NIC feature * NIC example
|
Hi @Sandido, Your PR has some issues. Please fix the CI sequentially by following the order of
|
openapi-pipeline-app
bot
added
CI-FixRequiredOnFailure
and removed
CI-FixRequiredOnFailure
labels
This was referenced May 4, 2021
* Restore point and User Data features * Restore Point cleanup * Restore point ex 1 * restore point ex2 * restore point ex 3 * REstore point ex 4 * restore point ex 5 * restore point ex 6 * restore point ex 7 * restore point ex 8 * restore point ex 9 * restore point ex 10 * restore point ex 11 * restore point readme * user data feature cloudservice * user data ex 1 * user data ex 2 * user data ex 3 * user data ex 4 * user data ex 5
This was referenced May 12, 2021
This was referenced May 18, 2021
11 tasks
|
/azp run |
mkarmark
pushed a commit
to mkarmark/azure-rest-api-specs
that referenced
this pull request
Jul 21, 2021
* initial copy of files * API version updates * Deep deletion feature (Azure#14232) * Deep deletion feature * Deep deletion cleanup * Deep deletion cleanup 2 * Scheduled Events feature (Azure#14233) * Scheduled Events feature * Scheduled Events feature example * PatchSetting Assessment Mode Windows + Linux (Azure#14234) * PatchSetting assessment feature * PatchSetting assessment feature cleanup * Patchsetting example * Patchsetting example 2 * Patchsetting example 3 * Patchsetting example 4 * Patchsetting example 5 * Add network interface config schema to VM Network profile (Azure#14235) * NIC feature * NIC example * Restore point and User Data features (Azure#14243) * Restore point and User Data features * Restore Point cleanup * Restore point ex 1 * restore point ex2 * restore point ex 3 * REstore point ex 4 * restore point ex 5 * restore point ex 6 * restore point ex 7 * restore point ex 8 * restore point ex 9 * restore point ex 10 * restore point ex 11 * restore point readme * user data feature cloudservice * user data ex 1 * user data ex 2 * user data ex 3 * user data ex 4 * user data ex 5 * Fix broken links (Azure#14244) * Remove unnecessary examples * fix conflict Co-authored-by: arcturusZhang <ufo54153@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Copied from : #14121
This PR is to release the new version of Compute, 2021-03-01.
This release consists of these PR, all of which have been reviewed before:
Deep Deletion: #13657
Scheduled Events: #13351
PatchSetting Assessment mode: #13468
Network Interface Config :#13449 (Required and received ARM signoff)
Patchsetting Description : #13509
RestorePoint: #13219 (Required and received ARM signoff)
UserData: #13220
#14191
#14197
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Changelog
Please ensure to add changelog with 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
Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.
Please 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 there are following updates in the PR, ensure to request an approval from 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.