-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[NetAppFiles]Anf 26457 s360 linting remove backup policy details #23438
[NetAppFiles]Anf 26457 s360 linting remove backup policy details #23438
Conversation
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.10.4)] | new version | base version |
---|---|---|
netapp.json | 2022-09-01(335899b) | 2022-09-01(main) |
️️✔️
Breaking Change(Cross-Version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️
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-netapp-2022-09-01 | package-netapp-2022-09-01(335899b) | package-netapp-2022-09-01(main) |
The following errors/warnings exist before current PR submission:
Only 30 items are listed, please refer to log for more details.
Rule | Message |
---|---|
OperationsApiResponseSchema |
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-09-01/netapp.json#L59 |
ResourceNameRestriction |
The resource name parameter 'quotaLimitName' should be defined with a 'pattern' restriction. Location: Microsoft.NetApp/stable/2022-09-01/netapp.json#L255 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.NetApp/stable/2022-09-01/netapp.json#L530 |
PatchIdentityProperty |
The patch operation body parameter schema should contains property 'identity'. Location: Microsoft.NetApp/stable/2022-09-01/netapp.json#L558 |
UnSupportedPatchProperties |
The patch operation body parameter schema should not contains property name. Location: Microsoft.NetApp/stable/2022-09-01/netapp.json#L558 |
UnSupportedPatchProperties |
The patch operation body parameter schema should not contains property type. Location: Microsoft.NetApp/stable/2022-09-01/netapp.json#L558 |
UnSupportedPatchProperties |
The patch operation body parameter schema should not contains property location. Location: Microsoft.NetApp/stable/2022-09-01/netapp.json#L558 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.NetApp/stable/2022-09-01/netapp.json#L587 |
PostOperationAsyncResponseValidation |
An async POST operation is tracked via Azure-AsyncOperation header. Set 'final-state-via' property to 'location' on 'x-ms-long-running-operation-options' Location: Microsoft.NetApp/stable/2022-09-01/netapp.json#L612 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.NetApp/stable/2022-09-01/netapp.json#L637 |
CreateOperationAsyncResponseValidation |
An async PUT operation is tracked via Azure-AsyncOperation header. Set 'final-state-via' property to 'azure-async-operation' on 'x-ms-long-running-operation-options' Location: Microsoft.NetApp/stable/2022-09-01/netapp.json#L740 |
UnSupportedPatchProperties |
The patch operation body parameter schema should not contains property name. Location: Microsoft.NetApp/stable/2022-09-01/netapp.json#L808 |
UnSupportedPatchProperties |
The patch operation body parameter schema should not contains property type. Location: Microsoft.NetApp/stable/2022-09-01/netapp.json#L808 |
UnSupportedPatchProperties |
The patch operation body parameter schema should not contains property location. Location: Microsoft.NetApp/stable/2022-09-01/netapp.json#L808 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.NetApp/stable/2022-09-01/netapp.json#L840 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.NetApp/stable/2022-09-01/netapp.json#L882 |
CreateOperationAsyncResponseValidation |
Only 201 is the supported response code for PUT async response. Location: Microsoft.NetApp/stable/2022-09-01/netapp.json#L1043 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.NetApp/stable/2022-09-01/netapp.json#L1043 |
UnSupportedPatchProperties |
The patch operation body parameter schema should not contains property name. Location: Microsoft.NetApp/stable/2022-09-01/netapp.json#L1068 |
UnSupportedPatchProperties |
The patch operation body parameter schema should not contains property type. Location: Microsoft.NetApp/stable/2022-09-01/netapp.json#L1068 |
UnSupportedPatchProperties |
The patch operation body parameter schema should not contains property location. Location: Microsoft.NetApp/stable/2022-09-01/netapp.json#L1068 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.NetApp/stable/2022-09-01/netapp.json#L1103 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.NetApp/stable/2022-09-01/netapp.json#L1158 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.NetApp/stable/2022-09-01/netapp.json#L1220 |
PostOperationAsyncResponseValidation |
An async POST operation must set long running operation options 'x-ms-long-running-operation-options' Location: Microsoft.NetApp/stable/2022-09-01/netapp.json#L1239 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.NetApp/stable/2022-09-01/netapp.json#L1270 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.NetApp/stable/2022-09-01/netapp.json#L1390 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.NetApp/stable/2022-09-01/netapp.json#L1446 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.NetApp/stable/2022-09-01/netapp.json#L1591 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.NetApp/stable/2022-09-01/netapp.json#L1641 |
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️
ApiReadinessCheck succeeded [Detail] [Expand]
️⚠️
~[Staging] ServiceAPIReadinessTest: 0 Warnings warning [Detail]
API Test is not triggered due to precheck failure. Check pipeline log for details.
️️✔️
SwaggerAPIView succeeded [Detail] [Expand]
️️✔️
CadlAPIView succeeded [Detail] [Expand]
️️✔️
TypeSpecAPIView 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.
️️✔️
TypeSpec Validation succeeded [Detail] [Expand]
Validation passes for TypeSpec Validation.
️️✔️
PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
Swagger Generation Artifacts
|
Generated ApiView
|
@lirenhe Note this is not changing in this PR most likely python SDK is outdated, updated version has not been relesed yet, and does not include a previous change that was approved.
|
@lirenhe can we progress with this ? |
@ihsanali01 This has one review approval, can we move this along to clear s360 issue? |
The SDK breaking in python is not related to this PR. |
…re#23438) * Remove backupPolicyDetails, not used * remove x-ms-azure-resource from proxy resources snapshots and backups
ARM API Information (Control Plane)
This is to fix issues in s360
https://portal.azure-devex-tools.com/amekpis/linting/detail?errorId=78AD65DE-AA14-45CD-8979-743413242EBC
https://portal.azure-devex-tools.com/amekpis/linting/detail?errorId=FBB43145-CBCB-4770-A72A-EB592E505946
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.