[NetAppFiles] Anf 10301 net app files update swagger rest api to 2020 12 01 #13061
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, @audunn 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 |
|---|---|
| Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: allowLocalNfsFSUsersWithLdap Location: Microsoft.NetApp/stable/2020-12-01/netapp.json#L3165 |
|
| Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: ldapEnabled Location: Microsoft.NetApp/stable/2020-12-01/netapp.json#L3721 |
|
| Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: healthy Location: Microsoft.NetApp/stable/2020-12-01/netapp.json#L4944 |
|
| 'resourceIdentity' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.NetApp/stable/2020-12-01/netapp.json#L3476 |
️️✔️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): 115 Warnings warning [Detail]
Only 10 items are listed, please refer to log for more details.
- Compared Swaggers (Based on Oad v0.8.6)
- original: preview/2017-08-15/netapp.json <---> new: stable/2020-12-01/netapp.json
| Rule | Message |
|---|---|
| The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NetApp/netAppAccounts/{accountName}/capacityPools/{poolName}/volumes/{volumeName}/mountTargets' removed or restructured? Old: Microsoft.NetApp/preview/2017-08-15/netapp.json#L674:5 |
|
| The required parameter 'subscriptionId' was added in the new version. New: Microsoft.NetApp/stable/2020-12-01/netapp.json#L218:9 |
|
| The required parameter 'resourceGroupName' was added in the new version. New: Microsoft.NetApp/stable/2020-12-01/netapp.json#L218:9 |
|
| The required parameter 'api-version' was added in the new version. New: Microsoft.NetApp/stable/2020-12-01/netapp.json#L218:9 |
|
| The required parameter 'subscriptionId' was added in the new version. New: Microsoft.NetApp/stable/2020-12-01/netapp.json#L258:9 |
|
| The required parameter 'resourceGroupName' was added in the new version. New: Microsoft.NetApp/stable/2020-12-01/netapp.json#L258:9 |
|
| The required parameter 'accountName' was added in the new version. New: Microsoft.NetApp/stable/2020-12-01/netapp.json#L258:9 |
|
| The required parameter 'api-version' was added in the new version. New: Microsoft.NetApp/stable/2020-12-01/netapp.json#L258:9 |
|
| The required parameter 'subscriptionId' was added in the new version. New: Microsoft.NetApp/stable/2020-12-01/netapp.json#L352:9 |
|
| The required parameter 'resourceGroupName' was added in the new version. New: Microsoft.NetApp/stable/2020-12-01/netapp.json#L352:9 |
️⚠️[Staging] Cross Version BreakingChange (Base on stable version): 53 Warnings warning [Detail]
Only 10 items are listed, please refer to log for more details.
- Compared Swaggers (Based on Oad v0.8.6)
- original: stable/2020-11-01/netapp.json <---> new: stable/2020-12-01/netapp.json
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️⚠️[Staging] SDK Track2 Validation: 48 Warnings warning [Detail]
Only 10 items are listed, please refer to log for more details.
- The following tags are being changed in this PR
| Rule | Message |
|---|---|
| "readme":"netapp/resource-manager/readme.md", "tag":"package-netapp-2020-11-01", "details":"The schema 'OperationListResult' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
| "readme":"netapp/resource-manager/readme.md", "tag":"package-netapp-2020-11-01", "details":"The schema 'Operation-display' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
| "readme":"netapp/resource-manager/readme.md", "tag":"package-netapp-2020-11-01", "details":"The schema 'OperationProperties' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
| "readme":"netapp/resource-manager/readme.md", "tag":"package-netapp-2020-11-01", "details":"The schema 'ServiceSpecification' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
| "readme":"netapp/resource-manager/readme.md", "tag":"package-netapp-2020-11-01", "details":"The schema 'MetricSpecification' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
| "readme":"netapp/resource-manager/readme.md", "tag":"package-netapp-2020-11-01", "details":"The schema 'Dimension' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
| "readme":"netapp/resource-manager/readme.md", "tag":"package-netapp-2020-11-01", "details":"The schema 'volumeProperties-exportPolicy' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
| "readme":"netapp/resource-manager/readme.md", "tag":"package-netapp-2020-11-01", "details":"The schema 'volumeProperties-dataProtection' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
| "readme":"netapp/resource-manager/readme.md", "tag":"package-netapp-2020-11-01", "details":"The schema 'volumePatchProperties-exportPolicy' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
| "readme":"netapp/resource-manager/readme.md", "tag":"package-netapp-2020-11-01", "details":"The schema 'volumePatchProperties-dataProtection' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
️️✔️[Staging] PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️[Staging] SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
Swagger Generation Artifacts
|
|
Hi @audunn, Your PR has some issues. Please fix the CI sequentially by following the order of
|
This was referenced Feb 19, 2021
This was referenced Feb 19, 2021
openapi-pipeline-app
bot
added
CI-FixRequiredOnFailure
and removed
CI-FixRequiredOnFailure
labels
openapi-pipeline-app
bot
added
CI-FixRequiredOnFailure
CI-BreakingChange-Python
and removed
CI-FixRequiredOnFailure
labels
This reverts commit 4ed4e8d.
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
msyyc
approved these changes
Mar 10, 2021
|
For python, the breaking change is ok |
msyyc
approved these changes
Mar 10, 2021
This was referenced Mar 10, 2021
MirzaSikander
pushed a commit
to MirzaSikander/azure-rest-api-specs
that referenced
this pull request
Mar 22, 2021
… 12 01 (Azure#13061) * Add new api version folder * Apply 2020-12-01 changes * pretty * snapshot delete return code * snapshot is a proxy resource * Revert "snapshot is a proxy resource" This reverts commit 4ed4e8d. * Fix examples incorrect type * Remove multiplfOf limit causing rounding issue in validation * Remove name for snapshot policy, not allowed * Pretty * update api version in examples Co-authored-by: Audunn Baldvinsson <audunn.baldvinsson@netapp.com>
mkarmark
pushed a commit
to mkarmark/azure-rest-api-specs
that referenced
this pull request
Jul 21, 2021
… 12 01 (Azure#13061) * Add new api version folder * Apply 2020-12-01 changes * pretty * snapshot delete return code * snapshot is a proxy resource * Revert "snapshot is a proxy resource" This reverts commit 4ed4e8d. * Fix examples incorrect type * Remove multiplfOf limit causing rounding issue in validation * Remove name for snapshot policy, not allowed * Pretty * update api version in examples Co-authored-by: Audunn Baldvinsson <audunn.baldvinsson@netapp.com>
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 updates the Azure NetAppFiles to api version 2020-12-01
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.
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.