-
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
[Hub Generated] Review request for Microsoft.Capacity to add version stable/2022-03-01 #18244
[Hub Generated] Review request for Microsoft.Capacity to add version stable/2022-03-01 #18244
Conversation
Hi, @gaoyp830 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. vscswagger@microsoft.com |
Swagger Validation Report
|
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-2022-03 |
️❌
~[Staging] ApiReadinessCheck: 1 Errors, 0 Warnings failed [Detail]
Rule | Message |
---|---|
API Readiness check failed. Please make sure your service is deployed. |
"code: InvalidResourceType, message: The resource type 'operations' could not be found in the namespace 'Microsoft.Capacity' for api version '2022-03-01'. The supported api-versions are '2017-11-01, 2018-06-01, 2019-04-01, 2020-10-01-preview, 2017-11-01-beta, 2018-06-01-beta, 2019-04-01-beta, 2020-10-01-beta'." |
️️✔️
ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️
SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️⚠️
Cross-Version Breaking Changes: 9 Warnings warning [Detail]
- Compared Swaggers (Based on Oad v0.9.3)
- current:stable/2022-03-01/reservations.json compared with base:stable/2021-07-01/reservations.json
- current:stable/2022-03-01/reservations.json compared with base:preview/2020-10-01-preview/reservations.json
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
️️✔️
SDK Track2 Validation succeeded [Detail] [Expand]
Validation passes for SDKTrack2Validation
- The following tags are being changed in this PR
️️✔️
PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️
SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️
Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
[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 Generation Artifacts
|
Hi @gaoyp830, Your PR has some issues. Please fix the CI sequentially by following the order of
|
Hi, @gaoyp830 your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). |
Hi @weidongxu-microsoft could you please reapprove/take a look at this PR with the latest commit? The check "API Readiness Check" failed because we havent update manifest in our service with API version 2022-03-01 since this is a new version. We will add that new version once we get sign off on this PR. |
@gaoyp830 I am not sure why use |
@weidongxu-microsoft Thanks for the suggestion! '$' was added by mistake, I have removed them in the new commit. Please take a look and help merge the PR as I cannot merge it. Thanks again for the help! |
2 things to confirm:
|
Hi @weidongxu-microsoft ,
|
Merged. Seems RP roll-out is not completed. It is recommended to ask SDK after roll-out complete (or at least notify the expected completion date in SDK request). |
….Capacity to add version stable/2022-03-01 (#2263) Create to sync Azure/azure-rest-api-specs#18244 [ReCreate this PR](https://github.com/azure-resource-manager-schemas/compare/main...AzureSDKAutomation:sdkAuto/reservations?expand=1)
…stable/2022-03-01 (Azure#18244) * Adds base for updating Microsoft.Capacity from version stable/2021-07-01 to version 2022-03-01 * Updates readme * Updates API version in new specs and examples * Update with new changes * include quota.json in readme * Remove dollar sign for publisher id * Change name from FulfillmentCreatedDateTime to BenefitStartTime
This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
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.
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.
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.