-
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
Feature/cplat 2021 04 01 - Capacity Reservation related changes #15058
Feature/cplat 2021 04 01 - Capacity Reservation related changes #15058
Conversation
Hi, @hari-bodicherla 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 Validation Report
|
Rule | Message |
---|---|
The default tag contains multiple API versions swaggers. readme: specification/compute/resource-manager/readme.md tag: specification/compute/resource-manager/readme.md#tag-package-2021-04-01 |
️️✔️
ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️
SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️
Cross-Version Breaking Changes succeeded [Detail] [Expand]
There are no breaking changes.
️❌
[Staging] SDK Track2 Validation: 1 Errors, 0 Warnings failed [Detail]
- The following tags are being changed in this PR
Rule | Message |
---|---|
PreCheck/DuplicateSchema |
"readme":"compute/resource-manager/readme.md", "tag":"package-2021-04-01", "details":"Duplicate Schema named PurchasePlan -- properties.promotionCode: undefined => "$ref":"#/components/schemas/schemas:1501", "description":"The Offer Promotion Code." ; This error can be temporarily avoided by using the 'modelerfour.lenient-model-deduplication' setting. NOTE: This setting will be removed in a future version of @autorest/modelerfour; schemas should be updated to fix this issue sooner than that." |
💬 AutorestCore/Exception | "readme":"compute/resource-manager/readme.md", "tag":"package-2021-04-01", "details":"> Installing AutoRest extension '@microsoft.azure/openapi-validator' (1.8.0)" |
💬 AutorestCore/Exception | "readme":"compute/resource-manager/readme.md", "tag":"package-2021-04-01", "details":"> Installed AutoRest extension '@microsoft.azure/openapi-validator' (1.8.0->1.8.0)" |
The following errors/warnings exist before current PR submission:
Rule | Message |
---|---|
AutorestCore/Exception |
"readme":"compute/resource-manager/readme.md", "tag":"package-2021-04-01", "details":"Error: Plugin prechecker reported failure." |
💬 AutorestCore/Exception | "readme":"compute/resource-manager/readme.md", "tag":"package-2021-04-01", "details":"> Loading AutoRest extension '@autorest/modelerfour' (4.15.456->4.15.456)" |
💬 AutorestCore/Exception | "readme":"compute/resource-manager/readme.md", "tag":"package-2021-04-01-only", "details":"> Loading AutoRest extension '@microsoft.azure/openapi-validator' (1.8.0->1.8.0)" |
💬 AutorestCore/Exception | "readme":"compute/resource-manager/readme.md", "tag":"package-2021-04-01-only", "details":"> Loading AutoRest extension '@autorest/modelerfour' (4.15.456->4.15.456)" |
️️✔️
[Staging] PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️
[Staging] SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
Swagger Generation Artifacts
|
specification/compute/resource-manager/Microsoft.Compute/stable/2021-04-01/compute.json
Outdated
Show resolved
Hide resolved
specification/compute/resource-manager/Microsoft.Compute/stable/2021-04-01/compute.json
Show resolved
Hide resolved
specification/compute/resource-manager/Microsoft.Compute/stable/2021-04-01/compute.json
Show resolved
Hide resolved
@ArcturusZhang @Sandido will you help me review this PR? |
specification/compute/resource-manager/Microsoft.Compute/stable/2021-04-01/compute.json
Outdated
Show resolved
Hide resolved
specification/compute/resource-manager/Microsoft.Compute/stable/2021-04-01/compute.json
Outdated
Show resolved
Hide resolved
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
* initial copy of old files to new folder 2021-04-01 * api version update * Add SpotRestorePolicy to CRP's VM Scale Set Resource (#14692) * Resolve merge conflicts after branch recreation * Fix Lint error * update with changes mae in 2021-03-01 * Update compute.json * Update CreateAVmWithNetworkInterfaceConfiguration.json update example file also to fix breaking change naming issue. * Feature/cplat 2021 04 01 - Capacity Reservation related changes (#15058) * updated code * updated swagger with cr changes * updated swagger with cr changes * updated swagger with cr changes * updated swagger * updated swagger * updated swagger * Feature/cplat 2021 04 01 (#15070) * 2021-04 initial * 2021-04 examples and readme * adding CR VMSS changes * updating api version in example and description of CR profile Co-authored-by: Adam Sandor <adsandor@microsoft.com> Co-authored-by: Theodore Chang <thchan@microsoft.com> * Update compute.json * syncronizing 2021-04-01 swagger with changes made in 2021-03-01 Co-authored-by: Sandeep Vishnu <sandeepkv93@gmail.com> Co-authored-by: hari-bodicherla <43284966+hari-bodicherla@users.noreply.github.com> Co-authored-by: micahjo <69926788+micahjo@users.noreply.github.com> Co-authored-by: Adam Sandor <adsandor@microsoft.com>
* initial copy of old files to new folder 2021-04-01 * api version update * Add SpotRestorePolicy to CRP's VM Scale Set Resource (Azure#14692) * Resolve merge conflicts after branch recreation * Fix Lint error * update with changes mae in 2021-03-01 * Update compute.json * Update CreateAVmWithNetworkInterfaceConfiguration.json update example file also to fix breaking change naming issue. * Feature/cplat 2021 04 01 - Capacity Reservation related changes (Azure#15058) * updated code * updated swagger with cr changes * updated swagger with cr changes * updated swagger with cr changes * updated swagger * updated swagger * updated swagger * Feature/cplat 2021 04 01 (Azure#15070) * 2021-04 initial * 2021-04 examples and readme * adding CR VMSS changes * updating api version in example and description of CR profile Co-authored-by: Adam Sandor <adsandor@microsoft.com> Co-authored-by: Theodore Chang <thchan@microsoft.com> * Update compute.json * syncronizing 2021-04-01 swagger with changes made in 2021-03-01 Co-authored-by: Sandeep Vishnu <sandeepkv93@gmail.com> Co-authored-by: hari-bodicherla <43284966+hari-bodicherla@users.noreply.github.com> Co-authored-by: micahjo <69926788+micahjo@users.noreply.github.com> Co-authored-by: Adam Sandor <adsandor@microsoft.com>
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.