Advanced ingress - ACA - Swagger API - DELETED - NEW PR - https://github.com/Azure/azure-rest-api-specs/pull/30862#30660
Advanced ingress - ACA - Swagger API - DELETED - NEW PR - https://github.com/Azure/azure-rest-api-specs/pull/30862#30660tdaroly wants to merge 12 commits intoAzure:release-app-Microsoft.App-2024-08-02-previewfrom tdaroly:tdarolywala/advanced-ingress-routing
Conversation
Next Steps to MergeNext steps that must be taken to merge this PR:
|
Generated ApiView
|
|
Choose a PR Template description and add a description to this pr to have the Purpose of PR and due diligence sections added |
| "properties": { | ||
| "tags": { | ||
| "type": "object", | ||
| "additionalProperties": { |
There was a problem hiding this comment.
There was a problem hiding this comment.
this is the PATCH response. Why would this need to be an array ? Could you give me an example spec of using arrays to for PATCH request/response ?
There was a problem hiding this comment.
@razvanbadea-msft can we resolve this conversation? this pattern is similar to all other tag props in the CommonDefintions spec
There was a problem hiding this comment.
We dont need to add tags property as it is included with tracked property reference.
Refer
There was a problem hiding this comment.
This does not need explicit declaration as it gets included with tracked resource definition
There was a problem hiding this comment.
This is for PATCH response and i see other resources using this pattern.
Managed Cert
Cert
Can we keep this pattern ?
...ication/app/resource-manager/Microsoft.App/preview/2024-08-02-preview/CommonDefinitions.json
Outdated
Show resolved
Hide resolved
...ication/app/resource-manager/Microsoft.App/preview/2024-08-02-preview/CommonDefinitions.json
Outdated
Show resolved
Hide resolved
| } | ||
| } | ||
| }, | ||
| "HttpRouteMatch": { |
There was a problem hiding this comment.
can you have prefix and path and pathSeparatedPrefix set at once? In place of having this properties that could grow in number, an enum property like
matchType with [Prefix, CaseSensitivePath, Path, PathSeparatedPrefix] and a matchValue string. In this way if another criteria will be needed youii could only have to add a new value to the enum
There was a problem hiding this comment.
No, some of these are mutually exclusive.
This matches the Envoy API we are exposing, we're trying not to diverge from that so that
- it's easier to expose additional envoy APIs in the future
- it's easier for customers to understand each field's behavior from ACA or envoy docs
- it's easier to validate the format of each field
- it's simpler usage. You'll normally only be setting one field. The enum would always require two fields, the type and the value
...ation/app/resource-manager/Microsoft.App/preview/2024-08-02-preview/ManagedEnvironments.json
Outdated
Show resolved
Hide resolved
|
Fix the Swagger PrettierCheck and Swagger ModelValidation checks |
...ication/app/resource-manager/Microsoft.App/preview/2024-08-02-preview/CommonDefinitions.json
Outdated
Show resolved
Hide resolved
...ication/app/resource-manager/Microsoft.App/preview/2024-08-02-preview/CommonDefinitions.json
Outdated
Show resolved
Hide resolved
...ication/app/resource-manager/Microsoft.App/preview/2024-08-02-preview/CommonDefinitions.json
Outdated
Show resolved
Hide resolved
...ication/app/resource-manager/Microsoft.App/preview/2024-08-02-preview/CommonDefinitions.json
Outdated
Show resolved
Hide resolved
...ication/app/resource-manager/Microsoft.App/preview/2024-08-02-preview/CommonDefinitions.json
Outdated
Show resolved
Hide resolved
| "properties": { | ||
| "tags": { | ||
| "type": "object", | ||
| "additionalProperties": { |
There was a problem hiding this comment.
We dont need to add tags property as it is included with tracked property reference.
Refer
...ication/app/resource-manager/Microsoft.App/preview/2024-08-02-preview/CommonDefinitions.json
Outdated
Show resolved
Hide resolved
| "properties": { | ||
| "tags": { | ||
| "type": "object", | ||
| "additionalProperties": { |
There was a problem hiding this comment.
This does not need explicit declaration as it gets included with tracked resource definition
...ication/app/resource-manager/Microsoft.App/preview/2024-08-02-preview/CommonDefinitions.json
Outdated
Show resolved
Hide resolved
...ication/app/resource-manager/Microsoft.App/preview/2024-08-02-preview/CommonDefinitions.json
Outdated
Show resolved
Hide resolved
...ication/app/resource-manager/Microsoft.App/preview/2024-08-02-preview/CommonDefinitions.json
Outdated
Show resolved
Hide resolved
...ation/app/resource-manager/Microsoft.App/preview/2024-08-02-preview/ManagedEnvironments.json
Outdated
Show resolved
Hide resolved
...ation/app/resource-manager/Microsoft.App/preview/2024-08-02-preview/ManagedEnvironments.json
Outdated
Show resolved
Hide resolved
...ation/app/resource-manager/Microsoft.App/preview/2024-08-02-preview/ManagedEnvironments.json
Outdated
Show resolved
Hide resolved
...ation/app/resource-manager/Microsoft.App/preview/2024-08-02-preview/ManagedEnvironments.json
Outdated
Show resolved
Hide resolved
|
PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts. |
NEW PR: #30862
Choose a PR Template
Switch to "Preview" on this description then select one of the choices below.
Click here to open a PR for a Data Plane API.
Click here to open a PR for a Control Plane (ARM) API.