[Hub Generated] Review request for Microsoft.AzureStackHCI to add version stable/2022-03-01 #18537
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, @sugatt 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 |
|---|---|
| Consider using x-ms-client-flatten to provide a better end user experience Location: Microsoft.AzureStackHCI/stable/2022-03-01/clusters.json#L757 |
|
| OperationId should contain the verb: 'createarcidentity' in:'ArcSettings_CreateIdentity'. Consider updating the operationId Location: Microsoft.AzureStackHCI/stable/2022-03-01/arcSettings.json#L267 |
|
| OperationId should contain the verb: 'createclusteridentity' in:'Clusters_CreateIdentity'. Consider updating the operationId Location: Microsoft.AzureStackHCI/stable/2022-03-01/clusters.json#L355 |
|
| 'PasswordCredential' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.AzureStackHCI/stable/2022-03-01/arcSettings.json#L472 |
|
| 'secretText' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.AzureStackHCI/stable/2022-03-01/arcSettings.json#L475 |
|
| 'keyId' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.AzureStackHCI/stable/2022-03-01/arcSettings.json#L478 |
|
| 'startDateTime' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.AzureStackHCI/stable/2022-03-01/arcSettings.json#L481 |
|
| 'endDateTime' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.AzureStackHCI/stable/2022-03-01/arcSettings.json#L485 |
|
| 'ArcIdentityResponseProperties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.AzureStackHCI/stable/2022-03-01/arcSettings.json#L504 |
|
| 'arcApplicationClientId' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.AzureStackHCI/stable/2022-03-01/arcSettings.json#L507 |
|
| 'arcApplicationTenantId' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.AzureStackHCI/stable/2022-03-01/arcSettings.json#L510 |
|
| 'arcServicePrincipalObjectId' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.AzureStackHCI/stable/2022-03-01/arcSettings.json#L513 |
|
| 'arcApplicationObjectId' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.AzureStackHCI/stable/2022-03-01/arcSettings.json#L516 |
|
| 'RawCertificateData' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.AzureStackHCI/stable/2022-03-01/clusters.json#L742 |
|
| 'certificates' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.AzureStackHCI/stable/2022-03-01/clusters.json#L745 |
|
| 'UploadCertificateRequest' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.AzureStackHCI/stable/2022-03-01/clusters.json#L754 |
|
| 'ClusterIdentityResponseProperties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.AzureStackHCI/stable/2022-03-01/clusters.json#L774 |
|
| 'aadClientId' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.AzureStackHCI/stable/2022-03-01/clusters.json#L777 |
|
| 'aadTenantId' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.AzureStackHCI/stable/2022-03-01/clusters.json#L780 |
|
| 'aadServicePrincipalObjectId' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.AzureStackHCI/stable/2022-03-01/clusters.json#L783 |
|
| 'aadApplicationObjectId' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.AzureStackHCI/stable/2022-03-01/clusters.json#L786 |
|
| Do not have duplicate name of x-ms-example, make sure every x-ms-example name unique. Duplicate x-ms-example: Create cluster Location: Microsoft.AzureStackHCI/stable/2022-03-01/operations.json#L43 |
The following errors/warnings exist before current PR submission:
| Rule | Message |
|---|---|
|
Missing identifier id in array item property Location: Microsoft.AzureStackHCI/stable/2022-03-01/arcSettings.json#L423 |
|
Missing identifier id in array item property Location: Microsoft.AzureStackHCI/stable/2022-03-01/extensions.json#L370 |
| Based on the response model schema, operation 'Operations_List' might be pageable. Consider adding the x-ms-pageable extension. Location: Microsoft.AzureStackHCI/stable/2022-03-01/operations.json#L38 |
|
| Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: autoUpgradeMinorVersion Location: Microsoft.AzureStackHCI/stable/2022-03-01/extensions.json#L458 |
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️❌~[Staging] 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 '2022-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'." |
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️⚠️Cross-Version Breaking Changes: 1 Warnings warning [Detail]
- Compared Swaggers (Based on Oad v0.9.3)
- current:stable/2022-03-01/arcSettings.json compared with base:stable/2022-01-01/arcSettings.json
- current:stable/2022-03-01/arcSettings.json compared with base:preview/2021-01-01-preview/arcSettings.json
- current:stable/2022-03-01/clusters.json compared with base:stable/2022-01-01/clusters.json
- current:stable/2022-03-01/clusters.json compared with base:preview/2021-01-01-preview/clusters.json
- current:stable/2022-03-01/extensions.json compared with base:stable/2022-01-01/extensions.json
- current:stable/2022-03-01/extensions.json compared with base:preview/2021-01-01-preview/extensions.json
- current:stable/2022-03-01/operations.json compared with base:stable/2022-01-01/operations.json
- current:stable/2022-03-01/operations.json compared with base:preview/2021-01-01-preview/operations.json
| Rule | Message |
|---|---|
| The read only property has changed from 'true' to 'false'. New: Microsoft.AzureStackHCI/stable/2022-03-01/arcSettings.json#L377:9 Old: Microsoft.AzureStackHCI/preview/2021-01-01-preview/arcSettings.json#L280:9 |
️❌CredScan: 0 Errors, 0 Warnings failed [Detail]
️️✔️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
|
This was referenced Apr 4, 2022
|
Approving PR get reviewed in azure-rest-api-specs-pr repo: https://github.com/Azure/azure-rest-api-specs-pr/pull/6260 |
changlong-liu
approved these changes
Apr 5, 2022
This was referenced Apr 5, 2022
ghost
pushed a commit
to Azure/azure-resource-manager-schemas
that referenced
this pull request
Apr 5, 2022
…t.AzureStackHCI to add version stable/2022-03-01 (#2296) Create to sync Azure/azure-rest-api-specs#18537 [ReCreate this PR](https://github.com/azure-resource-manager-schemas/compare/main...AzureSDKAutomation:sdkAuto/azurestackhci?expand=1)
FredericHeem
pushed a commit
to grucloud/azure-rest-api-specs
that referenced
this pull request
May 16, 2022
…sion stable/2022-03-01 (Azure#18537) * Adds base for updating Microsoft.AzureStackHCI from version stable/2022-01-01 to version 2022-03-01 * Updates readme * Updates API version in new specs and examples * Adding API version 2022-03-01 * Fix version in example files * Field name fixes
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.
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.