-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Appgw: Remove 499 status code from custom error page #24095
Appgw: Remove 499 status code from custom error page #24095
Conversation
Hi, @prateek2211 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 |
---|---|---|
applicationGateway.json | 2023-02-01(0c93bb5) | 2022-11-01(main) |
The following breaking changes are detected by comparison with the latest stable version:
Rule | Message |
---|---|
1019 - RemovedEnumValue |
The new version is removing enum value(s) 'HttpStatus499' from the old version. New: Microsoft.Network/stable/2023-02-01/applicationGateway.json#L3747:9 Old: Microsoft.Network/stable/2022-11-01/applicationGateway.json#L3747:9 |
️⚠️
LintDiff: 0 Warnings warning [Detail]
compared tags (via openapi-validator v2.1.2) | new version | base version |
---|---|---|
package-2023-02 | package-2023-02(0c93bb5) | package-2023-02(release-network-Microsoft.Network-official-2023-02-01) |
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 'applicationGatewayName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2023-02-01/applicationGateway.json#L37 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.Network/stable/2023-02-01/applicationGateway.json#L72 |
LroErrorContent |
Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: Microsoft.Network/stable/2023-02-01/applicationGateway.json#L84 |
LroErrorContent |
Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: Microsoft.Network/stable/2023-02-01/applicationGateway.json#L194 |
PatchIdentityProperty |
The patch operation body parameter schema should contains property 'identity'. Location: Microsoft.Network/stable/2023-02-01/applicationGateway.json#L234 |
ResourceNameRestriction |
The resource name parameter 'applicationGatewayName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2023-02-01/applicationGateway.json#L351 |
LroPostReturn |
200 response for a LRO POST operation must have a response schema specified. Location: Microsoft.Network/stable/2023-02-01/applicationGateway.json#L352 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.Network/stable/2023-02-01/applicationGateway.json#L389 |
LroErrorContent |
Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: Microsoft.Network/stable/2023-02-01/applicationGateway.json#L395 |
ResourceNameRestriction |
The resource name parameter 'applicationGatewayName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2023-02-01/applicationGateway.json#L405 |
LroPostReturn |
200 response for a LRO POST operation must have a response schema specified. Location: Microsoft.Network/stable/2023-02-01/applicationGateway.json#L406 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.Network/stable/2023-02-01/applicationGateway.json#L443 |
LroErrorContent |
Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: Microsoft.Network/stable/2023-02-01/applicationGateway.json#L449 |
ResourceNameRestriction |
The resource name parameter 'applicationGatewayName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2023-02-01/applicationGateway.json#L459 |
ParametersInPost |
$expand is a query parameter. Post operation must not contain any query parameter other than api-version. Location: Microsoft.Network/stable/2023-02-01/applicationGateway.json#L471 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.Network/stable/2023-02-01/applicationGateway.json#L507 |
LroErrorContent |
Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: Microsoft.Network/stable/2023-02-01/applicationGateway.json#L513 |
ResourceNameRestriction |
The resource name parameter 'applicationGatewayName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2023-02-01/applicationGateway.json#L523 |
ParametersInPost |
$expand is a query parameter. Post operation must not contain any query parameter other than api-version. Location: Microsoft.Network/stable/2023-02-01/applicationGateway.json#L535 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.Network/stable/2023-02-01/applicationGateway.json#L580 |
LroErrorContent |
Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: Microsoft.Network/stable/2023-02-01/applicationGateway.json#L586 |
ResourceNameRestriction |
The resource name parameter 'applicationGatewayName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2023-02-01/applicationGateway.json#L596 |
ResourceNameRestriction |
The resource name parameter 'applicationGatewayName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2023-02-01/applicationGateway.json#L649 |
ResourceNameRestriction |
The resource name parameter 'connectionName' should be defined with a 'pattern' restriction. Location: Microsoft.Network/stable/2023-02-01/applicationGateway.json#L649 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.Network/stable/2023-02-01/applicationGateway.json#L691 |
LroErrorContent |
Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: Microsoft.Network/stable/2023-02-01/applicationGateway.json#L703 |
ProvisioningStateSpecifiedForLROPut |
201 response schema in long running PUT operation is missing ProvisioningState property. A LRO PUT operations response schema must have ProvisioningState specified for the 200 and 201 status codes. Location: Microsoft.Network/stable/2023-02-01/applicationGateway.json#L712 |
PutResponseSchemaDescription |
Any Put MUST contain 200 and 201 return codes. Location: Microsoft.Network/stable/2023-02-01/applicationGateway.json#L756 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.Network/stable/2023-02-01/applicationGateway.json#L763 |
LroErrorContent |
Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: Microsoft.Network/stable/2023-02-01/applicationGateway.json#L769 |
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️❌
SwaggerAPIView: 0 Errors, 0 Warnings failed [Detail]
️️✔️
CadlAPIView succeeded [Detail] [Expand]
️️✔️
TypeSpecAPIView 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.
️️✔️
TypeSpec Validation succeeded [Detail] [Expand]
Validation passes for TypeSpec Validation.
️️✔️
PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
Swagger Generation Artifacts
|
Generated ApiView
|
Thank you for your contribution prateek2211! We will review the pull request and get back to you soon. |
Hi @prateek2211, 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. |
@JeffreyRichter help to approve this breaking change, Thanks |
@microsoft-github-policy-service agree company="Microsoft" |
@JackTn Can you please review this? |
All checks pass. Need merge now ? @prateek2211 |
@JackTn Yes, please merge this now. |
@msyyc help to merge this , Thanks |
@msyyc Can we merge this now? |
9b1ecde
into
Azure:release-network-Microsoft.Network-official-2023-02-01
* Adds base for updating Microsoft.Network from version stable/2022-11-01 to version 2023-02-01 * Updates readme * Updates API version in new specs and examples * Fixed double header issue (#23896) * Edited description for additional nics (#24071) * swagger 20230201 adding resource guid (#24154) * Appgw: Remove 499 status code from custom error page (#24095) * Add AdminState Property to Virtual Network Gateway Resource Properties (#23978) * add adminstate * update description * add headers to 202 * prettier fix * AppGW: Add default predefined ssl policy field in resource (#24094) * Fix examples (#24274) --------- Co-authored-by: Mikhail <[email protected]> Co-authored-by: JainRah <[email protected]> Co-authored-by: sssharma24 <[email protected]> Co-authored-by: Prateek Sachan <[email protected]> Co-authored-by: nimaller <[email protected]> Co-authored-by: Sindhu Aluguvelli <[email protected]>
* Adds base for updating Microsoft.Network from version stable/2022-11-01 to version 2023-02-01 * Updates readme * Updates API version in new specs and examples * Fixed double header issue (Azure#23896) * Edited description for additional nics (Azure#24071) * swagger 20230201 adding resource guid (Azure#24154) * Appgw: Remove 499 status code from custom error page (Azure#24095) * Add AdminState Property to Virtual Network Gateway Resource Properties (Azure#23978) * add adminstate * update description * add headers to 202 * prettier fix * AppGW: Add default predefined ssl policy field in resource (Azure#24094) * Fix examples (Azure#24274) --------- Co-authored-by: Mikhail <[email protected]> Co-authored-by: JainRah <[email protected]> Co-authored-by: sssharma24 <[email protected]> Co-authored-by: Prateek Sachan <[email protected]> Co-authored-by: nimaller <[email protected]> Co-authored-by: Sindhu Aluguvelli <[email protected]>
ARM API Information (Control Plane)
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. Note that this doesn't apply if you are trying to merge a PR that was previously in the private repository.
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.