-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Adding maximumFaultDomainCountSupported and currentCapacity property for the Capacity Reservation Resource in API Version 2022-08-01 #20076
Conversation
Hi, @grizzlytheodore 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 pipeline can not start as the pull request has merge conflicts. |
1 similar comment
Swagger pipeline can not start as the pull request has merge conflicts. |
Swagger pipeline started successfully. If there is ApiView generated, it will be updated in this comment. |
d9172c4
to
1282ab8
Compare
Swagger Validation Report
|
compared swaggers (via Oad v0.9.7)] | new version | base version |
---|---|---|
capacityReservation.json | 2022-08-01(ac62b81) | 2022-03-01(main) |
️⚠️
LintDiff: 0 Warnings warning [Detail]
compared tags (via openapi-validator v1.13.0) | new version | base version |
---|---|---|
package-2022-08-01 | package-2022-08-01(ac62b81) | package-2022-08-01(feature/cplat-2022-08-01) |
The following errors/warnings exist before current PR submission:
Rule | Message |
---|---|
Per the Noun_Verb convention for Operation Ids, the noun 'CapacityReservations' should not appear after the underscore. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: ComputeRP/stable/2022-08-01/capacityReservation.json#L670 |
|
Based on the response model schema, operation 'CapacityReservationGroups_Get' might be pageable. Consider adding the x-ms-pageable extension. Location: ComputeRP/stable/2022-08-01/capacityReservation.json#L212 |
|
Based on the response model schema, operation 'CapacityReservations_Get' might be pageable. Consider adding the x-ms-pageable extension. Location: ComputeRP/stable/2022-08-01/capacityReservation.json#L595 |
|
'CapacityReservationGroupInstanceView' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: ComputeRP/stable/2022-08-01/capacityReservation.json#L720 |
️⚠️
Avocado: 1 Warnings warning [Detail]
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-2022-08-01 |
️️✔️
ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️
SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️❌
SDK Track2 Validation: 1 Errors, 0 Warnings failed [Detail]
- The following tags are being changed in this PR
- "https://github.com/Azure/azure-rest-api-specs/blob/ac62b81c7b900d7a2f579289efb7b1612c4a745b/specification/compute/resource-manager/readme.md#tag-package-2022-08-01">compute/resource-manager/readme.md#package-2022-08-01
- "https://github.com/Azure/azure-rest-api-specs/blob/ac62b81c7b900d7a2f579289efb7b1612c4a745b/specification/compute/resource-manager/readme.md#tag-package-2022-08-01-only">compute/resource-manager/readme.md#package-2022-08-01-only
Rule | Message |
---|---|
PreCheck/DuplicateSchema |
"readme":"compute/resource-manager/readme.md", "tag":"package-2022-08-01", "details":"Duplicate Schema named 'PurchasePlan' (1 differences):\n - properties.promotionCode: => "$ref":"#/components/schemas/schemas:1402", "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." |
The following errors/warnings exist before current PR submission:
Rule | Message |
---|---|
|
"readme":"compute/resource-manager/readme.md", "tag":"package-2022-08-01", "details":"Error: 1 errors occured -- cannot continue." |
"readme":"compute/resource-manager/readme.md", "tag":"package-2022-08-01-only", "details":"Security scheme azure_auth is unknown and will not be processed. Only supported types are AADToken, AzureKey, Anonymous" |
️️✔️
PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️
SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️
CadlValidation succeeded [Detail] [Expand]
Validation passes for CadlValidation.
Swagger Generation Artifacts
|
Generated ApiView
|
Hi @grizzlytheodore, Your PR has some issues. Please fix the CI sequentially by following the order of
|
for some reason, it's not letting me set this as approved, but approving verbally |
...pute/resource-manager/Microsoft.Compute/ComputeRP/stable/2022-08-01/capacityReservation.json
Outdated
Show resolved
Hide resolved
...22-08-01/examples/capacityReservationExamples/CapacityReservation_Update_MaximumSet_Gen.json
Show resolved
Hide resolved
...pute/resource-manager/Microsoft.Compute/ComputeRP/stable/2022-08-01/capacityReservation.json
Outdated
Show resolved
Hide resolved
@@ -23,6 +23,7 @@ | |||
{ | |||
"name": "myCapacityReservation1", | |||
"utilizationInfo": { | |||
"currentCapacity": 5, |
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.
In this and other example files for capacity reservation change expand parameter wherever specified to $expand.
@@ -10,6 +10,7 @@ | |||
"200": { | |||
"body": { | |||
"properties": { | |||
"platformFaultDomainCount": 3, |
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.
pls. add the $expand = instanceView parameter in the request parameters as this example is also returning the instance view in the response.
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
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 appy to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review. Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.
-[ ] 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.