[NetAppFiles] Anf 20508 update for 2022-03-01 #19534
Merged
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. vscswagger@microsoft.com |
Swagger Validation Report
|
| compared swaggers (via Oad v0.9.6)] | new version | base version |
|---|---|---|
| netapp.json | 2022-03-01(0746eb3) | 2022-01-01(main) |
| netapp.json | 2022-03-01(0746eb3) | 2021-04-01(main) |
The following breaking changes are detected by comparison with the latest preview version:
Only 30 items are listed, please refer to log for more details.
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️⚠️LintDiff: 2 Warnings warning [Detail]
| compared tags (via openapi-validator v1.13.0) | new version | base version |
|---|---|---|
| package-netapp-2022-03-01 | package-netapp-2022-03-01(0746eb3) | default(main) |
The following errors/warnings are introduced by current PR:
| Rule | Message |
|---|---|
| Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: coolAccess Location: Microsoft.NetApp/stable/2022-03-01/netapp.json#L4949 |
|
| Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: coolAccess Location: Microsoft.NetApp/stable/2022-03-01/netapp.json#L5884 |
The following errors/warnings exist before current PR submission:
Only 30 items are listed, please refer to log for more details.
| Rule | Message |
|---|---|
|
The response schema of operations API '/providers/Microsoft.NetApp/operations' does not match the ARM specification. Please standardize the schema. Location: Microsoft.NetApp/stable/2022-03-01/netapp.json#L40 |
|
The schema 'OperationListResult' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.NetApp/stable/2022-03-01/netapp.json#L4060 |
|
The schema 'display' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.NetApp/stable/2022-03-01/netapp.json#L4083 |
|
The schema 'OperationProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.NetApp/stable/2022-03-01/netapp.json#L4115 |
|
The schema 'ServiceSpecification' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.NetApp/stable/2022-03-01/netapp.json#L4124 |
|
The schema 'MetricSpecification' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.NetApp/stable/2022-03-01/netapp.json#L4149 |
|
The schema 'Dimension' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.NetApp/stable/2022-03-01/netapp.json#L4252 |
|
The schema 'exportPolicy' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.NetApp/stable/2022-03-01/netapp.json#L5081 |
|
The schema 'dataProtection' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.NetApp/stable/2022-03-01/netapp.json#L5227 |
|
The schema 'exportPolicy' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.NetApp/stable/2022-03-01/netapp.json#L5818 |
|
The schema 'dataProtection' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.NetApp/stable/2022-03-01/netapp.json#L5840 |
|
The schema 'cloudError' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.NetApp/stable/2022-03-01/netapp.json#L6910 |
|
The schema 'cloudErrorBody' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.NetApp/stable/2022-03-01/netapp.json#L6920 |
| 'GET' operation 'Volumes_ReplicationStatus' should use method name 'Get' or Method name start with 'List'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.NetApp/stable/2022-03-01/netapp.json#L1323 |
|
| Based on the response model schema, operation 'Volumes_Get' might be pageable. Consider adding the x-ms-pageable extension. Location: Microsoft.NetApp/stable/2022-03-01/netapp.json#L866 |
|
| Based on the response model schema, operation 'SnapshotPolicies_ListVolumes' might be pageable. Consider adding the x-ms-pageable extension. Location: Microsoft.NetApp/stable/2022-03-01/netapp.json#L2404 |
|
| The child tracked resource, 'capacityPools' with immediate parent 'netAppAccount', must have a list by immediate parent operation. Location: Microsoft.NetApp/stable/2022-03-01/netapp.json#L4744 |
|
| The child tracked resource, 'volumes' with immediate parent 'capacityPool', must have a list by immediate parent operation. Location: Microsoft.NetApp/stable/2022-03-01/netapp.json#L4973 |
|
| The child tracked resource, 'snapshots' with immediate parent 'volume', must have a list by immediate parent operation. Location: Microsoft.NetApp/stable/2022-03-01/netapp.json#L5992 |
|
| The child tracked resource, 'snapshotPolicies' with immediate parent 'netAppAccount', must have a list by immediate parent operation. Location: Microsoft.NetApp/stable/2022-03-01/netapp.json#L6100 |
|
| The child tracked resource, 'accountBackups' with immediate parent 'netAppAccount', must have a list by immediate parent operation. Location: Microsoft.NetApp/stable/2022-03-01/netapp.json#L6405 |
|
| The child tracked resource, 'backups' with immediate parent 'volume', must have a list by immediate parent operation. Location: Microsoft.NetApp/stable/2022-03-01/netapp.json#L6405 |
|
| The child tracked resource, 'backupPolicies' with immediate parent 'netAppAccount', must have a list by immediate parent operation. Location: Microsoft.NetApp/stable/2022-03-01/netapp.json#L6592 |
|
| Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: forceDelete Location: Microsoft.NetApp/stable/2022-03-01/netapp.json#L1064 |
|
| Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enableRegionalMdmAccount Location: Microsoft.NetApp/stable/2022-03-01/netapp.json#L4194 |
|
| Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: fillGapWithZero Location: Microsoft.NetApp/stable/2022-03-01/netapp.json#L4220 |
|
| Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isInternal Location: Microsoft.NetApp/stable/2022-03-01/netapp.json#L4232 |
|
| Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isAvailable Location: Microsoft.NetApp/stable/2022-03-01/netapp.json#L4269 |
|
| Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: aesEncryption Location: Microsoft.NetApp/stable/2022-03-01/netapp.json#L4654 |
|
| Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: ldapSigning Location: Microsoft.NetApp/stable/2022-03-01/netapp.json#L4658 |
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️ApiReadinessCheck 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.
️⚠️SDK Track2 Validation: 1 Warnings warning [Detail]
- The following tags are being changed in this PR
- "https://github.com/Azure/azure-rest-api-specs/blob/0746eb3259cbb00420c5f0b2ef6389cf23c01294/specification/netapp/resource-manager/readme.md#tag-package-netapp-2022-03-01">netapp/resource-manager/readme.md#package-netapp-2022-03-01
| Rule | Message |
|---|---|
| "readme":"netapp/resource-manager/readme.md", "tag":"package-netapp-2022-03-01", "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.
️️✔️Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
️️✔️CadlValidation succeeded [Detail] [Expand]
Validation passes for CadlValidation.
Swagger Generation Artifacts
|
audunn
changed the title
openapi-workflow-bot
bot
added
ARMReview
WaitForARMFeedback
|
Hi, @audunn your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). |
|
Hi @audunn, Your PR has some issues. Please fix the CI sequentially by following the order of
|
|
NewApiVersionRequired reason: |
This was referenced Jun 20, 2022
Closed
This was referenced Jun 20, 2022
Closed
rkmanda
added
the
ARMSignedOff
openapi-workflow-bot
bot
removed
the
WaitForARMFeedback
|
@audunn Please help to address the |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
tadelesh
approved these changes
Jul 20, 2022
This was referenced Jul 20, 2022
Closed
Closed
ghost
pushed a commit
to Azure/azure-resource-manager-schemas
that referenced
this pull request
Jul 20, 2022
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
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.