2020-12-01 Compute Rest API version Release #12334
Merged
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
* new * new
sync forked repo
sync forked swagger repo
…e Resources and edgeZone parameter for image discovery APIs (#11199) * Added Extended location property to Microsoft.Compute VM, VMSS & Image resources * Add edgeZone parameter for image discovery APIs Co-authored-by: Pavan Rachapudy <vrachapu@microsoft.com> Co-authored-by: Vishnu Priya Ananthu Sundaram <viananth@microsoft.com>
.Net SDK failures seem to be the usual ones with the Automation failing and a Permission Denied log. These are expected and not due to the PR.
…s to RollingUpgradePolicy for VMSS (#11184)
…ies in AssessPatches API and patch settings in Windows and Linux Configuration in VMModel (#11768)
… example and port VM force delete changes to this version (#11770)
* Made changes for UefiSettings and SecurityType * Prettier ran * updated description and properties. * Made changes for UefiSettings and SecurityType * Prettier ran * updated description and properties. * Remove None as SecurityType * Changing name from SecureBoot to TrustedLaunch
* Updating installPatchesinput parameter in installPatches API * Updating enum values
…te and recommended usage to get up-to-date sizes using APIs (#11598) * Removing vmSizeTyes enum. * Updating description to remove & update the deprecated links. * Revert enum removal and update description with tobe deprecated note * Updating deprecation message. * Fix prettier Co-authored-by: Avinash Akka <avakka@microsoft.com>
* Add ImageFeatures to the PIR consumption API * remove excess comma * fix typo * move changes to 2020-12 * revert whitespace for good measure Co-authored-by: Grace Liang <grlian@microsoft.com>
This was referenced Feb 4, 2021
11 tasks
JeffreyRichter
added
the
Approved-BreakingChange
8 tasks
|
/azp run |
This was referenced May 18, 2021
mkarmark
pushed a commit
to mkarmark/azure-rest-api-specs
that referenced
this pull request
Jul 21, 2021
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.
Work for the Azure Compute Rest API version 2020-12-01.
Aggregated rom the following Swagger PRs:
-Readme:
#12623
#12348
-DiskRP:
#12521
-Features:
#11441
#11184
#11620
#11770
ExtendedLocation: #11199
#11409
#11554
#11598
#11771
#11768
#12295
OrchestrationMode: #12062
#12295
#12018
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 API 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.