[Hub Generated] Review request for Microsoft.AzureStackHCI to add version stable/2023-03-01 #23255
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
|
Hi, @priyjain358 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 |
ghost
added
the
Swagger Validation Report
|
| compared swaggers (via Oad v0.10.4)] | new version | base version |
|---|---|---|
| arcSettings.json | 2023-03-01(0b9b6d3) | 2023-02-01(main) |
| arcSettings.json | 2023-03-01(0b9b6d3) | 2021-09-01-preview(main) |
| clusters.json | 2023-03-01(0b9b6d3) | 2023-02-01(main) |
| clusters.json | 2023-03-01(0b9b6d3) | 2021-09-01-preview(main) |
| extensions.json | 2023-03-01(0b9b6d3) | 2023-02-01(main) |
| extensions.json | 2023-03-01(0b9b6d3) | 2021-09-01-preview(main) |
| offers.json | 2023-03-01(0b9b6d3) | 2023-02-01(main) |
| operations.json | 2023-03-01(0b9b6d3) | 2023-02-01(main) |
| operations.json | 2023-03-01(0b9b6d3) | 2021-09-01-preview(main) |
| publishers.json | 2023-03-01(0b9b6d3) | 2023-02-01(main) |
| skus.json | 2023-03-01(0b9b6d3) | 2023-02-01(main) |
| updateRuns.json | 2023-03-01(0b9b6d3) | 2023-02-01(main) |
| updateSummaries.json | 2023-03-01(0b9b6d3) | 2023-02-01(main) |
| updates.json | 2023-03-01(0b9b6d3) | 2023-02-01(main) |
The following breaking changes are detected by comparison with the latest preview version:
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️⚠️LintDiff: 0 Warnings warning [Detail]
| compared tags (via openapi-validator v2.0.0) | new version | base version |
|---|---|---|
| package-2023-03 | package-2023-03(0b9b6d3) | default(main) |
The following errors/warnings exist before current PR submission:
| Rule | Message |
|---|---|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.AzureStackHCI/stable/2023-03-01/arcSettings.json#L701 |
|
| Schema should have a description or title. Location: Microsoft.AzureStackHCI/stable/2023-03-01/arcSettings.json#L708 |
|
| Schema should have a description or title. Location: Microsoft.AzureStackHCI/stable/2023-03-01/arcSettings.json#L740 |
|
| Schema should have a description or title. Location: Microsoft.AzureStackHCI/stable/2023-03-01/clusters.json#L904 |
|
| Schema should have a description or title. Location: Microsoft.AzureStackHCI/stable/2023-03-01/clusters.json#L916 |
|
| Consider using x-ms-client-flatten to provide a better end user experience Location: Microsoft.AzureStackHCI/stable/2023-03-01/clusters.json#L919 |
|
| Schema should have a description or title. Location: Microsoft.AzureStackHCI/stable/2023-03-01/clusters.json#L925 |
|
| Schema should have a description or title. Location: Microsoft.AzureStackHCI/stable/2023-03-01/clusters.json#L942 |
|
| Consider using x-ms-client-flatten to provide a better end user experience Location: Microsoft.AzureStackHCI/stable/2023-03-01/clusters.json#L945 |
|
| Schema should have a description or title. Location: Microsoft.AzureStackHCI/stable/2023-03-01/clusters.json#L962 |
|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.AzureStackHCI/stable/2023-03-01/extensions.json#L553 |
|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.AzureStackHCI/stable/2023-03-01/extensions.json#L566 |
|
| 'PUT' operation 'UpdateRuns_Put' should use method name 'Create'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.AzureStackHCI/stable/2023-03-01/updateRuns.json#L140 |
|
| 'PUT' operation 'Updates_Put' should use method name 'Create'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.AzureStackHCI/stable/2023-03-01/updates.json#L186 |
|
| Schema should have a description or title. Location: Microsoft.AzureStackHCI/stable/2023-03-01/updates.json#L526 |
|
| Schema should have a description or title. Location: Microsoft.AzureStackHCI/stable/2023-03-01/updates.json#L538 |
|
| Schema should have a description or title. Location: Microsoft.AzureStackHCI/stable/2023-03-01/updates.json#L553 |
|
| OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'UpdateSummariesModel'. Consider using the plural form of 'UpdateSummaries' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.AzureStackHCI/stable/2023-03-01/updateSummaries.json#L39 |
|
| OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'UpdateSummariesModel'. Consider using the plural form of 'UpdateSummaries' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.AzureStackHCI/stable/2023-03-01/updateSummaries.json#L81 |
|
| OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'UpdateSummariesModel'. Consider using the plural form of 'UpdateSummaries' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.AzureStackHCI/stable/2023-03-01/updateSummaries.json#L131 |
|
| 'PUT' operation 'UpdateSummaries_Put' should use method name 'Create'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.AzureStackHCI/stable/2023-03-01/updateSummaries.json#L131 |
|
| OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'UpdateSummariesModel'. Consider using the plural form of 'UpdateSummaries' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.AzureStackHCI/stable/2023-03-01/updateSummaries.json#L177 |
|
| Schema should have a description or title. Location: Microsoft.AzureStackHCI/stable/2023-03-01/updateSummaries.json#L374 |
|
| Schema should have a description or title. Location: Microsoft.AzureStackHCI/stable/2023-03-01/updateSummaries.json#L389 |
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️❌ApiReadinessCheck: 1 Errors, 0 Warnings failed [Detail]
| Rule | Message |
|---|---|
|
"code: InvalidResourceType, message: The resource type 'operations' could not be found in the namespace 'Microsoft.AzureStackHCI' for api version '2023-03-01'. The supported api-versions are '2020-03-01-preview, 2020-10-01, 2020-11-01-preview, 2021-01-01-preview, 2021-07-01-preview, 2021-09-01-preview, 2021-09-01, 2022-01-01, 2022-03-01, 2022-05-01, 2022-08-01-preview, 2022-09-01, 2022-10-01, 2022-12-01, 2022-12-15-preview, 2023-02-01'." |
️❌~[Staging] ServiceAPIReadinessTest: 0 Errors, 0 Warnings failed [Detail]
Tag package-2023-03; Prod region: Not deployed; Canary region: Not deployed
️️✔️SwaggerAPIView succeeded [Detail] [Expand]
️️✔️CadlAPIView succeeded [Detail] [Expand]
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️️✔️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).
️️✔️CadlValidation succeeded [Detail] [Expand]
Validation passes for CadlValidation.
️️✔️PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
Swagger Generation Artifacts
|
Generated ApiView
|
|
Hi @priyjain358 and @arcboard, one or more change(s) have been detected in your Arc enabled VM's or Arc enabled Server's RPs. Please review the changes and ensure that no gaps have been introduced with respect to the ARM API modeling consistency across Azure Arc and Azure Compute. For further details, see guidelines at Consistency in ARM Modeling. To approve the change(s), set the label to ArcSignedOff. If you have any questions, please mail to arcboard@microsoft.com. |
openapi-workflow-bot
bot
added
ARMReview
WaitForARMFeedback
|
Hi, @priyjain358 your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). |
|
This api version has already been reviewed and merged into the private repo: https://github.com/Azure/azure-rest-api-specs-pr/pull/11574 |
This was referenced Mar 23, 2023
AzureRestAPISpecReview
added
new-api-version
ReadyForApiTest
This was referenced Mar 23, 2023
|
API Readiness check doesn't apply to us since we are RPaaS RP. It was ignored previously as well: #22578 |
|
Signing off on the basis of : https://github.com/Azure/azure-rest-api-specs-pr/pull/11574 |
raosuhas
added
the
ARMSignedOff
openapi-workflow-bot
bot
removed
the
WaitForARMFeedback
lirenhe
approved these changes
Mar 24, 2023
This was referenced Mar 24, 2023
JoshLove-msft
pushed a commit
to JoshLove-msft/azure-rest-api-specs
that referenced
this pull request
Apr 25, 2023
…sion stable/2023-03-01 (Azure#23255) * Adds base for updating Microsoft.AzureStackHCI from version stable/2023-02-01 to version 2023-03-01 * Updates readme * Updates API version in new specs and examples * Consent and Disable APIs added * add managed by for extensions * prettier fix
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.
ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo. If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:
Contribution checklist (MS Employees Only):
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 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 copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For 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 you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.