-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Clean properties which are never used #22423
Clean properties which are never used #22423
Conversation
Hi, @chinadragon0515 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 |
---|---|---|
ManagedEnvironments.json | 2022-11-01-preview(990ed8b) | 2022-10-01(main) |
ManagedEnvironments.json | 2022-11-01-preview(990ed8b) | 2022-06-01-preview(main) |
The following breaking changes are detected by comparison with the latest stable version:
The following breaking changes are detected by comparison with the latest preview version:
️⚠️
LintDiff: 0 Warnings warning [Detail]
compared tags (via openapi-validator v2.0.0) | new version | base version |
---|---|---|
package-preview-2022-11 | package-preview-2022-11(990ed8b) | package-preview-2022-11(release-app-Microsoft.App-2022-11-01-preview) |
The following errors/warnings exist before current PR submission:
Only 30 items are listed, please refer to log for more details.
Rule | Message |
---|---|
ResourceNameRestriction |
The resource name parameter 'environmentName' should be defined with a 'pattern' restriction. Location: Microsoft.App/preview/2022-11-01-preview/ManagedEnvironments.json#L101 |
CreateOperationAsyncResponseValidation |
An async PUT operation must set long running operation options 'x-ms-long-running-operation-options' Location: Microsoft.App/preview/2022-11-01-preview/ManagedEnvironments.json#L147 |
DeleteOperationAsyncResponseValidation |
An async DELETE operation must set long running operation options 'x-ms-long-running-operation-options' Location: Microsoft.App/preview/2022-11-01-preview/ManagedEnvironments.json#L208 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.App/preview/2022-11-01-preview/ManagedEnvironments.json#L237 |
UnSupportedPatchProperties |
The patch operation body parameter schema should not contains property name. Location: Microsoft.App/preview/2022-11-01-preview/ManagedEnvironments.json#L278 |
UnSupportedPatchProperties |
The patch operation body parameter schema should not contains property type. Location: Microsoft.App/preview/2022-11-01-preview/ManagedEnvironments.json#L278 |
UnSupportedPatchProperties |
The patch operation body parameter schema should not contains property location. Location: Microsoft.App/preview/2022-11-01-preview/ManagedEnvironments.json#L278 |
PatchBodyParametersSchema |
Properties of a PATCH request body must not be required, property:location. Location: Microsoft.App/preview/2022-11-01-preview/ManagedEnvironments.json#L283 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.App/preview/2022-11-01-preview/ManagedEnvironments.json#L298 |
GetCollectionResponseSchema |
The response in the GET collection operation 'Certificates_List' does not match the response definition in the individual GET operation 'Certificates_Get' . Location: Microsoft.App/preview/2022-11-01-preview/ManagedEnvironments.json#L316 |
ResourceNameRestriction |
The resource name parameter 'environmentName' should be defined with a 'pattern' restriction. Location: Microsoft.App/preview/2022-11-01-preview/ManagedEnvironments.json#L316 |
ResourceNameRestriction |
The resource name parameter 'environmentName' should be defined with a 'pattern' restriction. Location: Microsoft.App/preview/2022-11-01-preview/ManagedEnvironments.json#L366 |
ResourceNameRestriction |
The resource name parameter 'certificateName' should be defined with a 'pattern' restriction. Location: Microsoft.App/preview/2022-11-01-preview/ManagedEnvironments.json#L366 |
ResourceNameRestriction |
The resource name parameter 'environmentName' should be defined with a 'pattern' restriction. Location: Microsoft.App/preview/2022-11-01-preview/ManagedEnvironments.json#L594 |
ResourceNameRestriction |
The resource name parameter 'managedCertificateName' should be defined with a 'pattern' restriction. Location: Microsoft.App/preview/2022-11-01-preview/ManagedEnvironments.json#L594 |
GetCollectionResponseSchema |
The response in the GET collection operation 'ManagedCertificates_List' does not match the response definition in the individual GET operation 'ManagedCertificates_Get' . Location: Microsoft.App/preview/2022-11-01-preview/ManagedEnvironments.json#L836 |
ResourceNameRestriction |
The resource name parameter 'environmentName' should be defined with a 'pattern' restriction. Location: Microsoft.App/preview/2022-11-01-preview/ManagedEnvironments.json#L836 |
ResourceNameRestriction |
The resource name parameter 'environmentName' should be defined with a 'pattern' restriction. Location: Microsoft.App/preview/2022-11-01-preview/ManagedEnvironments.json#L886 |
ResourceNameRestriction |
The resource name parameter 'environmentName' should be defined with a 'pattern' restriction. Location: Microsoft.App/preview/2022-11-01-preview/ManagedEnvironments.json#L945 |
ResourceNameRestriction |
The resource name parameter 'environmentName' should be defined with a 'pattern' restriction. Location: Microsoft.App/preview/2022-11-01-preview/ManagedEnvironments.json#L992 |
Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition Location: Microsoft.App/preview/2022-11-01-preview/ManagedEnvironments.json#L26 |
|
Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition Location: Microsoft.App/preview/2022-11-01-preview/ManagedEnvironments.json#L66 |
|
Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition Location: Microsoft.App/preview/2022-11-01-preview/ManagedEnvironments.json#L109 |
|
The x-ms-long-running-operation-options should be specified explicitly to indicate the type of response header to track the async operation. Location: Microsoft.App/preview/2022-11-01-preview/ManagedEnvironments.json#L147 |
|
Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition Location: Microsoft.App/preview/2022-11-01-preview/ManagedEnvironments.json#L154 |
|
The x-ms-long-running-operation-options should be specified explicitly to indicate the type of response header to track the async operation. Location: Microsoft.App/preview/2022-11-01-preview/ManagedEnvironments.json#L208 |
|
Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition Location: Microsoft.App/preview/2022-11-01-preview/ManagedEnvironments.json#L215 |
|
The x-ms-long-running-operation-options should be specified explicitly to indicate the type of response header to track the async operation. Location: Microsoft.App/preview/2022-11-01-preview/ManagedEnvironments.json#L257 |
|
Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition Location: Microsoft.App/preview/2022-11-01-preview/ManagedEnvironments.json#L264 |
|
Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition Location: Microsoft.App/preview/2022-11-01-preview/ManagedEnvironments.json#L324 |
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️
SwaggerAPIView succeeded [Detail] [Expand]
️️✔️
CadlAPIView succeeded [Detail] [Expand]
️️✔️
ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️
SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️
PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️
SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️
CadlValidation succeeded [Detail] [Expand]
Validation passes for CadlValidation.
️️✔️
PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
Swagger Generation Artifacts
|
Generated ApiView
|
87da38d
to
9820307
Compare
Hi @chinadragon0515, Your PR has some issues. Please fix the CI sequentially by following the order of
|
Hi @chinadragon0515, one or multiple breaking change(s) is detected in your PR. Please check out the breaking change(s), and provide business justification in the PR comment and @ PR assignee why you must have these change(s), and how external customer impact can be mitigated. Please ensure to follow breaking change policy to request breaking change review and approval before proceeding swagger PR review. |
Create breaking review https://msazure.visualstudio.com/One/_workitems/edit/16986590 |
9820307
to
aafbc0b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need breaking change approval for main branch merge
...rce-manager/Microsoft.App/preview/2022-11-01-preview/examples/ManagedEnvironments_Patch.json
Outdated
Show resolved
Hide resolved
Breaking change is approved |
aafbc0b
to
990ed8b
Compare
ARM API Information (Control Plane)
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.