Swagger correctness and completeness for RecoveryServices #12932
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, @amchandn 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 |
Swagger Validation Report
|
| Rule | Message |
|---|---|
| The child tracked resource, 'operationStatus' with immediate parent 'Vault', must have a list by immediate parent operation. Location: Microsoft.RecoveryServices/stable/2020-10-01/vaultusages.json#L65 |
|
| The child tracked resource, 'operationResults' with immediate parent 'Vault', must have a list by immediate parent operation. Location: Microsoft.RecoveryServices/stable/2020-10-01/vaultusages.json#L65 |
|
| Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: useSystemAssignedIdentity Location: Microsoft.RecoveryServices/stable/2020-10-01/vaults.json#L1564 |
|
| 'operationId' parameter lacks 'description' property. Consider adding a 'description' element. Accurate description is essential for maintaining reference documentation. Location: Microsoft.RecoveryServices/stable/2020-10-01/vaults.json#L725 |
|
| 'operationId' parameter lacks 'description' property. Consider adding a 'description' element. Accurate description is essential for maintaining reference documentation. Location: Microsoft.RecoveryServices/stable/2020-10-01/vaults.json#L776 |
|
| 'systemData' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.RecoveryServices/stable/2020-10-01/vaults.json#L1132 |
|
| 'keyVaultProperties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.RecoveryServices/stable/2020-10-01/vaults.json#L1313 |
|
| 'kekIdentity' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.RecoveryServices/stable/2020-10-01/vaults.json#L1316 |
|
| 'error' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.RecoveryServices/stable/2020-10-01/vaults.json#L1609 |
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️[Staging] Cross Version BreakingChange (Base on preview version) succeeded [Detail] [Expand]
There are no breaking changes.
️⚠️[Staging] Cross Version BreakingChange (Base on stable version): 6 Warnings warning [Detail]
- Compared Swaggers (Based on Oad v0.8.6)
- original: stable/2020-02-02/registeredidentities.json <---> new: stable/2020-10-01/registeredidentities.json
- original: stable/2020-02-02/replicationusages.json <---> new: stable/2020-10-01/replicationusages.json
- original: stable/2020-02-02/vaults.json <---> new: stable/2020-10-01/vaults.json
- original: stable/2020-02-02/vaultusages.json <---> new: stable/2020-10-01/vaultusages.json
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️⚠️[Staging] SDK Track2 Validation: 4 Warnings warning [Detail]
- The following tags are being changed in this PR
| Rule | Message |
|---|---|
| "readme":"recoveryservices/resource-manager/readme.md", "tag":"package-2020-10", "details":"The schema 'CloudError' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
| "readme":"recoveryservices/resource-manager/readme.md", "tag":"package-2020-10", "details":"The schema 'Error' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
| "readme":"recoveryservices/resource-manager/readme.md", "tag":"package-2020-10", "details":"The schema 'ErrorAdditionalInfo' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
| "readme":"recoveryservices/resource-manager/readme.md", "tag":"package-2020-10", "details":"Checking for duplicate schemas, this could take a (long) while. Run with --verbose for more detail." |
️️✔️[Staging] PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️[Staging] SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
|
Swagger pipeline restarted successfully, please wait for status update in this comment. |
This was referenced Feb 10, 2021
|
In the Window Period to fix mismatches between swagger and service, when PR is labelled with “FixS360”, breaking change can be approved by PR assignee; the Azure Breaking Change Board is no longer required to approve the PR. Please ensure to clarify what s360 action items to be solved, and @ mention PR assignee for awareness. Please check this wiki Window to Fix Broken for more details. |
|
Hi, @amchandn your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). cc @markcowl |
openapi-workflow-bot
bot
added
the
WaitForARMFeedback
|
@markcowl , the following tests have not ran for my latest iteration and have been in expected state for a couple of hours now..
|
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
/azp run Swagger |
|
No pipelines are associated with this pull request. |
|
/azp run CredScan |
|
No pipelines are associated with this pull request. |
|
/azp run Swagger Avocado |
|
No pipelines are associated with this pull request. |
varunkumta
added
ARMSignedOff
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
markcowl
approved these changes
Feb 16, 2021
This was referenced Feb 16, 2021
mkarmark
pushed a commit
to mkarmark/azure-rest-api-specs
that referenced
this pull request
Jul 21, 2021
* Adding recoveryservices swagger for 2020-10-01 * Changing default api-version in readme.md * Changing sku.tier to string * Fixing api-version * Testing changes to 2016-06-01 * Adding missing definitions * Reverting case change for eTag * restoring vaults.json * prettier fix * Adding systemData to Vaults * Adding definition of systemData * restoring registeredidentities.json
11 tasks
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.
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.
Answer: already deployed
Answer: 12 February
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 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.