[ContainerApp] Support peer traffic encryption.#28159
[ContainerApp] Support peer traffic encryption.#28159LGDoor merged 1 commit intorelease-app-Microsoft.App-2024-03-01from
Conversation
Next Steps to MergeNext steps that must be taken to merge this PR:
|
Swagger Validation Report
|
| compared swaggers (via Oad v0.10.5)] | new version | base version |
|---|---|---|
| ManagedEnvironments.json | 2024-03-01(28e2077) | 2023-05-01(main) |
| ManagedEnvironments.json | 2024-03-01(28e2077) | 2023-11-02-preview(main) |
The following breaking changes are detected by comparison with the latest preview version:
️⚠️LintDiff: 3 Warnings warning [Detail]
| compared tags (via openapi-validator v2.2.0) | new version | base version |
|---|---|---|
| package-2024-03 | package-2024-03(28e2077) | package-2024-03(release-app-Microsoft.App-2024-03-01) |
[must fix]The following errors/warnings are introduced by current PR:
| Rule | Message | Related RPC [For API reviewers] |
|---|---|---|
| Consider using x-ms-client-flatten to provide a better end user experience Location: Microsoft.App/stable/2024-03-01/ManagedEnvironments.json#L1263 |
||
| Consider using x-ms-client-flatten to provide a better end user experience Location: Microsoft.App/stable/2024-03-01/ManagedEnvironments.json#L1267 |
||
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.App/stable/2024-03-01/ManagedEnvironments.json#L1271 |
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/stable/2024-03-01/ManagedEnvironments.json#L101 |
LroErrorContent |
Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: Microsoft.App/stable/2024-03-01/ManagedEnvironments.json#L197 |
DeleteResponseCodes |
Long-running delete operations must have responses with 202, 204 and default return codes. They also must have no other response codes. Location: Microsoft.App/stable/2024-03-01/ManagedEnvironments.json#L211 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.App/stable/2024-03-01/ManagedEnvironments.json#L240 |
LroErrorContent |
Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: Microsoft.App/stable/2024-03-01/ManagedEnvironments.json#L249 |
PatchBodyParametersSchema |
Properties of a PATCH request body must not be required, property:location. Location: Microsoft.App/stable/2024-03-01/ManagedEnvironments.json#L286 |
LroLocationHeader |
A 202 response should include an Location response header. Location: Microsoft.App/stable/2024-03-01/ManagedEnvironments.json#L301 |
LroErrorContent |
Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: Microsoft.App/stable/2024-03-01/ManagedEnvironments.json#L307 |
ResourceNameRestriction |
The resource name parameter 'environmentName' should be defined with a 'pattern' restriction. Location: Microsoft.App/stable/2024-03-01/ManagedEnvironments.json#L319 |
ResourceNameRestriction |
The resource name parameter 'environmentName' should be defined with a 'pattern' restriction. Location: Microsoft.App/stable/2024-03-01/ManagedEnvironments.json#L369 |
ResourceNameRestriction |
The resource name parameter 'certificateName' should be defined with a 'pattern' restriction. Location: Microsoft.App/stable/2024-03-01/ManagedEnvironments.json#L369 |
PutResponseCodes |
Synchronous and long-running PUT operations must have responses with 200, 201 and default return codes. They also must not have other response codes. Location: Microsoft.App/stable/2024-03-01/ManagedEnvironments.json#L422 |
ResourceNameRestriction |
The resource name parameter 'environmentName' should be defined with a 'pattern' restriction. Location: Microsoft.App/stable/2024-03-01/ManagedEnvironments.json#L597 |
ResourceNameRestriction |
The resource name parameter 'managedCertificateName' should be defined with a 'pattern' restriction. Location: Microsoft.App/stable/2024-03-01/ManagedEnvironments.json#L597 |
PutResponseCodes |
Synchronous and long-running PUT operations must have responses with 200, 201 and default return codes. They also must not have other response codes. Location: Microsoft.App/stable/2024-03-01/ManagedEnvironments.json#L650 |
NoErrorCodeResponses |
Invalid status code specified. Please refer to the documentation for the allowed set. Location: Microsoft.App/stable/2024-03-01/ManagedEnvironments.json#L703 |
LroErrorContent |
Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: Microsoft.App/stable/2024-03-01/ManagedEnvironments.json#L710 |
ResourceNameRestriction |
The resource name parameter 'environmentName' should be defined with a 'pattern' restriction. Location: Microsoft.App/stable/2024-03-01/ManagedEnvironments.json#L839 |
ResourceNameRestriction |
The resource name parameter 'environmentName' should be defined with a 'pattern' restriction. Location: Microsoft.App/stable/2024-03-01/ManagedEnvironments.json#L889 |
ResourceNameRestriction |
The resource name parameter 'environmentName' should be defined with a 'pattern' restriction. Location: Microsoft.App/stable/2024-03-01/ManagedEnvironments.json#L948 |
ResourceNameRestriction |
The resource name parameter 'environmentName' should be defined with a 'pattern' restriction. Location: Microsoft.App/stable/2024-03-01/ManagedEnvironments.json#L995 |
| Use the latest version v5 of types.json. Location: Microsoft.App/stable/2024-03-01/ManagedEnvironments.json#L28 |
|
| Use the latest version v5 of types.json. Location: Microsoft.App/stable/2024-03-01/ManagedEnvironments.json#L31 |
|
| Use the latest version v5 of types.json. Location: Microsoft.App/stable/2024-03-01/ManagedEnvironments.json#L68 |
|
| Use the latest version v5 of types.json. Location: Microsoft.App/stable/2024-03-01/ManagedEnvironments.json#L71 |
|
| Use the latest version v5 of types.json. Location: Microsoft.App/stable/2024-03-01/ManagedEnvironments.json#L74 |
|
| Use the latest version v5 of types.json. Location: Microsoft.App/stable/2024-03-01/ManagedEnvironments.json#L111 |
|
| Use the latest version v5 of types.json. Location: Microsoft.App/stable/2024-03-01/ManagedEnvironments.json#L114 |
|
| Use the latest version v5 of types.json. Location: Microsoft.App/stable/2024-03-01/ManagedEnvironments.json#L124 |
|
| Use the latest version v5 of types.json. Location: Microsoft.App/stable/2024-03-01/ManagedEnvironments.json#L156 |
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️SwaggerAPIView succeeded [Detail] [Expand]
️️✔️TypeSpecAPIView succeeded [Detail] [Expand]
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
️️✔️Automated merging requirements met succeeded [Detail] [Expand]
Swagger Generation Artifacts
|
Generated ApiView
|
| "type": "object", | ||
| "properties": { | ||
| "enabled": { | ||
| "type": "boolean", |
There was a problem hiding this comment.
Consider making this an Enum. Also please check the other Lint Diff warnings for this PR here :
There was a problem hiding this comment.
Thanks for your feedback. It's intended to keep consistent with the existing peerAuthentication.mtls.enabled which is also boolean. For the rest "AvoidNestedProperties" warnings, it isn't applicable here.
|
Please address or respond to feedback from the ARM API reviewer. |
* Adds base for updating Microsoft.App from version stable/2023-05-01 to version 2024-03-01 * Updates readme * Updates API version in new specs and examples * [ContainerApp] Support peer traffic encryption. (#28159) * fix (#28426) * Add new feature GPU and job diagnostics to 2024-03-01 (#27875) * fix * fix * Add more features to 2024-03-01 which are same with 2023-05-02-preview (#28369) * fix * fix * fix * update readme * add sdk-suppressions.yaml --------- Co-authored-by: Alancere <804873052@qq.com> --------- Co-authored-by: Xiangyang Yu <yyddxxmm@gmail.com> Co-authored-by: Alancere <804873052@qq.com>
ARM (Control Plane) API Specification Update Pull Request
Tip
Overwhelmed by all this guidance? See the
Getting helpsection at the bottom of this PR description.Note
As of January 2024 there is no PR assignee. This is expected. See https://aka.ms/azsdk/pr-arm-review.
PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.
Click here to see the details of Step 1, Breaking Changes review
If you are in purview of Step 1 of the diagram, follow the Breaking Changes review process.
IMPORTANT! This applies even if you believe your PR was mislabeled, for any reason, including tool failure.
Click here to see the details of Step 2, ARM review
See https://aka.ms/azsdk/pr-arm-review.
Click here to see the diagram footnotes
Diagram footnotes
[1] See ARM review queue (for PR merge queues, see [2]).
[2] public repo merge queue, private repo merge queue (for ARM review queue, [1])
The ARM reviewer on-call engineer visits the merge queue twice a day, so the approximate ETA for merges is 12 - 24 hours.
Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!
Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.
Additional information
Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the
Generated ApiViewcomment added to this PR. You can use ApiView to show API versions diff.Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.
Getting help
Purpose of this PRandDue diligence checklist.Next Steps to Mergecomment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.and https://aka.ms/ci-fix.
queuedstate, please add a comment with contents/azp run.This should result in a new comment denoting a
PR validation pipelinehas started and the checks should be updated after few minutes.