-
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
Add 202 status code for PrivateEndpointConnections_Delete #23404
Add 202 status code for PrivateEndpointConnections_Delete #23404
Conversation
Hi, @priyankarking 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. [email protected] |
Swagger Validation Report
|
compared swaggers (via Oad v0.10.4)] | new version | base version |
---|---|---|
redisenterprise.json | 2022-01-01(4fbe6a3) | 2022-01-01(main) |
Rule | Message |
---|---|
1011 - AddingResponseCode |
The new version adds a response code '202'. New: Microsoft.Cache/stable/2022-01-01/redisenterprise.json#L1073:11 |
1044 - XmsLongRunningOperationChanged |
The new version has a different 'x-ms-longrunning-operation' value than the previous one. New: Microsoft.Cache/stable/2022-01-01/redisenterprise.json#L1037:7 Old: Microsoft.Cache/stable/2022-01-01/redisenterprise.json#L1037:7 |
️️✔️
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-2022-01 | package-2022-01(4fbe6a3) | package-2022-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 |
---|---|
ResourceNameRestriction |
The resource name parameter 'clusterName' should be defined with a 'pattern' restriction. Location: Microsoft.Cache/stable/2022-01-01/redisenterprise.json#L115 |
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.Cache/stable/2022-01-01/redisenterprise.json#L116 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.Cache/stable/2022-01-01/redisenterprise.json#L220 |
DeleteOperationAsyncResponseValidation |
An async DELETE operation is tracked via Azure-AsyncOperation header. Set 'final-state-via' property to 'location' on 'x-ms-long-running-operation-options' Location: Microsoft.Cache/stable/2022-01-01/redisenterprise.json#L231 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.Cache/stable/2022-01-01/redisenterprise.json#L264 |
ResourceNameRestriction |
The resource name parameter 'clusterName' should be defined with a 'pattern' restriction. Location: Microsoft.Cache/stable/2022-01-01/redisenterprise.json#L400 |
ResourceNameRestriction |
The resource name parameter 'clusterName' should be defined with a 'pattern' restriction. Location: Microsoft.Cache/stable/2022-01-01/redisenterprise.json#L446 |
ResourceNameRestriction |
The resource name parameter 'databaseName' should be defined with a 'pattern' restriction. Location: Microsoft.Cache/stable/2022-01-01/redisenterprise.json#L446 |
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.Cache/stable/2022-01-01/redisenterprise.json#L447 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.Cache/stable/2022-01-01/redisenterprise.json#L562 |
DeleteOperationAsyncResponseValidation |
An async DELETE operation is tracked via Azure-AsyncOperation header. Set 'final-state-via' property to 'location' on 'x-ms-long-running-operation-options' Location: Microsoft.Cache/stable/2022-01-01/redisenterprise.json#L617 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.Cache/stable/2022-01-01/redisenterprise.json#L654 |
ResourceNameRestriction |
The resource name parameter 'clusterName' should be defined with a 'pattern' restriction. Location: Microsoft.Cache/stable/2022-01-01/redisenterprise.json#L669 |
ResourceNameRestriction |
The resource name parameter 'databaseName' should be defined with a 'pattern' restriction. Location: Microsoft.Cache/stable/2022-01-01/redisenterprise.json#L669 |
ResourceNameRestriction |
The resource name parameter 'clusterName' should be defined with a 'pattern' restriction. Location: Microsoft.Cache/stable/2022-01-01/redisenterprise.json#L715 |
ResourceNameRestriction |
The resource name parameter 'databaseName' should be defined with a 'pattern' restriction. Location: Microsoft.Cache/stable/2022-01-01/redisenterprise.json#L715 |
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.Cache/stable/2022-01-01/redisenterprise.json#L716 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.Cache/stable/2022-01-01/redisenterprise.json#L765 |
ResourceNameRestriction |
The resource name parameter 'clusterName' should be defined with a 'pattern' restriction. Location: Microsoft.Cache/stable/2022-01-01/redisenterprise.json#L777 |
ResourceNameRestriction |
The resource name parameter 'databaseName' should be defined with a 'pattern' restriction. Location: Microsoft.Cache/stable/2022-01-01/redisenterprise.json#L777 |
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.Cache/stable/2022-01-01/redisenterprise.json#L778 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.Cache/stable/2022-01-01/redisenterprise.json#L824 |
ResourceNameRestriction |
The resource name parameter 'clusterName' should be defined with a 'pattern' restriction. Location: Microsoft.Cache/stable/2022-01-01/redisenterprise.json#L836 |
ResourceNameRestriction |
The resource name parameter 'databaseName' should be defined with a 'pattern' restriction. Location: Microsoft.Cache/stable/2022-01-01/redisenterprise.json#L836 |
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.Cache/stable/2022-01-01/redisenterprise.json#L837 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.Cache/stable/2022-01-01/redisenterprise.json#L883 |
GetCollectionResponseSchema |
The response in the GET collection operation 'PrivateEndpointConnections_List' does not match the response definition in the individual GET operation 'PrivateEndpointConnections_Get' . Location: Microsoft.Cache/stable/2022-01-01/redisenterprise.json#L895 |
ResourceNameRestriction |
The resource name parameter 'clusterName' should be defined with a 'pattern' restriction. Location: Microsoft.Cache/stable/2022-01-01/redisenterprise.json#L895 |
ResourceNameRestriction |
The resource name parameter 'clusterName' should be defined with a 'pattern' restriction. Location: Microsoft.Cache/stable/2022-01-01/redisenterprise.json#L940 |
ResourceNameRestriction |
The resource name parameter 'privateEndpointConnectionName' should be defined with a 'pattern' restriction. Location: Microsoft.Cache/stable/2022-01-01/redisenterprise.json#L940 |
️️✔️
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
|
Hi @priyankarking, 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. |
...ache/preview/2023-03-01-preview/examples/RedisEnterpriseDeletePrivateEndpointConnection.json
Outdated
Show resolved
Hide resolved
18a963a
to
ae59724
Compare
ae59724
to
4fbe6a3
Compare
@msyyc I don't think we have JS braking... |
Co-authored-by: Priyankar Gupta <[email protected]>
…and update response examples
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 apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.
-[x] 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.