-
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
Capacity RP Quota APIs for GA #11930
Conversation
Swagger Validation Report
|
Rule | Message |
---|---|
A LRO Post operation with return schema must have 'x-ms-long-running-operation-options' extension enabled. New: Microsoft.Capacity/stable/2017-11-01/reservations.json#L227 |
|
A LRO Post operation with return schema must have 'x-ms-long-running-operation-options' extension enabled. New: Microsoft.Capacity/stable/2017-11-01/reservations.json#L180 |
|
'ErrorResponseCode' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. New: Microsoft.Capacity/stable/2017-11-01/reservations.json#L496 |
|
'capabilities' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. New: Microsoft.Capacity/stable/2017-11-01/reservations.json#L652 |
|
'SkuCapability' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. New: Microsoft.Capacity/stable/2017-11-01/reservations.json#L668 |
|
'provisioningState' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. New: Microsoft.Capacity/stable/2017-11-01/reservations.json#L767 |
|
'location' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. New: Microsoft.Capacity/stable/2017-11-01/reservations.json#L782 |
|
'provisioningState' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. New: Microsoft.Capacity/stable/2017-11-01/reservations.json#L840 |
|
'Error' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. New: Microsoft.Capacity/stable/2017-11-01/reservations.json#L970 |
|
'error' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. New: Microsoft.Capacity/stable/2017-11-01/reservations.json#L973 |
️⚠️
Avocado: 1 Warnings warning [Detail]
Rule | Message |
---|---|
The default tag contains multiple API versions swaggers. readme: specification/reservations/resource-manager/readme.md tag: specification/reservations/resource-manager/readme.md#tag-package-2020-10-25 |
️️✔️
ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️
SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️⚠️
[Staging] Cross Version BreakingChange (Base on preview version): 10 Warnings warning [Detail]
- Compared Swaggers (Based on Oad v0.8.1)
- original: preview/2019-07-19/quota.json <---> new: stable/2020-10-25/quota.json
Rule | Message |
---|---|
The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/providers/Microsoft.Capacity/autoQuotaIncrease' removed or restructured? New: azure-rest-api-specs/blob/b034d7f015609d46a6fec622581b54ef588f6418/ Old: Microsoft.Capacity/preview/2019-07-19/quota.json#L384:5 |
|
The new version is missing a definition that was found in the old version. Was 'autoQuotaIncreaseSettings' removed or renamed? New: Microsoft.Capacity/stable/2020-10-25/quota.json#L382:3 Old: Microsoft.Capacity/preview/2019-07-19/quota.json#L467:3 |
|
The new version is missing a definition that was found in the old version. Was 'aqiSettings' removed or renamed? New: Microsoft.Capacity/stable/2020-10-25/quota.json#L382:3 Old: Microsoft.Capacity/preview/2019-07-19/quota.json#L467:3 |
|
The new version is missing a definition that was found in the old version. Was 'SupportRequestAction' removed or renamed? New: Microsoft.Capacity/stable/2020-10-25/quota.json#L382:3 Old: Microsoft.Capacity/preview/2019-07-19/quota.json#L467:3 |
|
The new version is missing a definition that was found in the old version. Was 'AutoQuotaIncreaseDetail' removed or renamed? New: Microsoft.Capacity/stable/2020-10-25/quota.json#L382:3 Old: Microsoft.Capacity/preview/2019-07-19/quota.json#L467:3 |
|
The new version is missing a definition that was found in the old version. Was 'ContactMethod' removed or renamed? New: Microsoft.Capacity/stable/2020-10-25/quota.json#L382:3 Old: Microsoft.Capacity/preview/2019-07-19/quota.json#L467:3 |
|
The new version is missing a definition that was found in the old version. Was 'AqiState' removed or renamed? New: Microsoft.Capacity/stable/2020-10-25/quota.json#L382:3 Old: Microsoft.Capacity/preview/2019-07-19/quota.json#L467:3 |
|
The new version is missing a definition that was found in the old version. Was 'EmailActions' removed or renamed? New: Microsoft.Capacity/stable/2020-10-25/quota.json#L382:3 Old: Microsoft.Capacity/preview/2019-07-19/quota.json#L467:3 |
|
The new version is missing a definition that was found in the old version. Was 'Actions' removed or renamed? New: Microsoft.Capacity/stable/2020-10-25/quota.json#L382:3 Old: Microsoft.Capacity/preview/2019-07-19/quota.json#L467:3 |
|
The new version is missing a definition that was found in the old version. Was 'SeverityTypes' removed or renamed? New: Microsoft.Capacity/stable/2020-10-25/quota.json#L382:3 Old: Microsoft.Capacity/preview/2019-07-19/quota.json#L467:3 |
️️✔️
[Staging] Cross Version BreakingChange (Base on stable version) succeeded [Detail] [Expand]
There are no breaking changes.
Swagger Generation Artifacts
|
Please review it. |
@raych1 - The issues are fixed. It looks like there was a bad merge from master. |
@rahuls-microsoft , all the checks except JS SDK automation passes. Can you read through the |
Hi, @rahuls-microsoft your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). cc @xccc-msft |
Hi, @rahuls-microsoft 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 |
1 similar comment
Hi, @rahuls-microsoft 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 |
@rahuls-microsoft Your PR has a single commit with all the newly added files. Its hard to review the PR as I do not know what exactly changed from earlier preview version to GA version. To expedite the ARM review, I recommend to do first commit by copying all the earlier version files as is. From 2nd commit onwards, you can make the required GA changes. |
Hi, @rahuls-microsoft 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 |
Sure, This is a new version for GA. I can point to the Preview version. |
@rahuls-microsoft can you please submit a new PR with the first commit by copying all the earlier version files as is. From 2nd commit onwards, you can make the required GA changes. |
Preview version - https://github.com/Azure/azure-rest-api-specs/blob/master/specification/reservations/resource-manager/Microsoft.Capacity/preview/2019-07-19/quota.json |
Overwrote the files with Preview version and updated it to GA version. |
@RamyasreeChakka - Overwrote the files with Preview version checked in, then updated it to GA version. |
@leni-msft @raych1 @orquiri @lirenhe |
@xccc-msft , could you help with the follow-ups? |
@rahuls-microsoft Please let me know once it's ready to merge. Thanks. |
Yes, we are ready to merge. Please merge it. Thanks. |
* Capacity RP Quota APIs for GA * Adding preview version to stable dir as base files. * Files from preview version, which will be removed. * Updating to GA Version.
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.