Skip to content

Advanced ingress - ACA - Swagger API - DELETED - NEW PR - https://github.com/Azure/azure-rest-api-specs/pull/30862#30660

Closed
tdaroly wants to merge 12 commits intoAzure:release-app-Microsoft.App-2024-08-02-previewfrom
tdaroly:tdarolywala/advanced-ingress-routing
Closed

Advanced ingress - ACA - Swagger API - DELETED - NEW PR - https://github.com/Azure/azure-rest-api-specs/pull/30862#30660
tdaroly wants to merge 12 commits intoAzure:release-app-Microsoft.App-2024-08-02-previewfrom
tdaroly:tdarolywala/advanced-ingress-routing

Conversation

@tdaroly
Copy link
Contributor

@tdaroly tdaroly commented Sep 20, 2024

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.

@openapi-pipeline-app
Copy link

openapi-pipeline-app bot commented Sep 20, 2024

Next Steps to Merge

Next steps that must be taken to merge this PR:
  • ❌ This PR is in purview of the ARM review (label: ARMReview). This PR must get ARMSignedOff label from an ARM reviewer.
    This PR has ARMChangesRequested label. Please address or respond to feedback from the ARM API reviewer.
    When you are ready to continue the ARM API review, please remove the ARMChangesRequested label.
    Automation should then add WaitForARMFeedback label.
    ❗If you don't have permissions to remove the label, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories.
    For details of the ARM review, see aka.ms/azsdk/pr-arm-review
  • ❌ The required check named Automated merging requirements met has failed. This is the final check that must pass. Refer to the check in the PR's 'Checks' tab for details on how to fix it and consult the aka.ms/ci-fix guide. In addition, refer to step 4 in the PR workflow diagram

@openapi-pipeline-app
Copy link

openapi-pipeline-app bot commented Sep 20, 2024

@razvanbadea-msft
Copy link
Member

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": {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

additionalProperties

ARM is trying to reduce instances of unschematized APIs to make it easier for consumers of those APIs to understand them and use them reliably, not to mention provide better support in the various SDKs.

Please make this an array or provide an explanation for why you need this.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@razvanbadea-msft can we resolve this conversation? this pattern is similar to all other tag props in the CommonDefintions spec

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We dont need to add tags property as it is included with tracked property reference.
Refer

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This does not need explicit declaration as it gets included with tracked resource definition

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is for PATCH response and i see other resources using this pattern.

Managed Cert

Cert

Can we keep this pattern ?

}
}
},
"HttpRouteMatch": {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

HttpRouteMatch

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

Copy link
Contributor

@Tratcher Tratcher Sep 20, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

@razvanbadea-msft
Copy link
Member

Fix the Swagger PrettierCheck and Swagger ModelValidation checks

@openapi-pipeline-app openapi-pipeline-app bot removed the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Sep 20, 2024
@tdaroly tdaroly changed the title Tdarolywala/advanced ingress routing Advanced ingress - ACA - Swagger API Oct 3, 2024
"properties": {
"tags": {
"type": "object",
"additionalProperties": {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We dont need to add tags property as it is included with tracked property reference.
Refer

"properties": {
"tags": {
"type": "object",
"additionalProperties": {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This does not need explicit declaration as it gets included with tracked resource definition

@openapi-pipeline-app
Copy link

PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts.

@tdaroly tdaroly closed this by deleting the head repository Oct 4, 2024
@tdaroly tdaroly changed the title Advanced ingress - ACA - Swagger API Advanced ingress - ACA - Swagger API - DELETED - NEW PR - https://github.com/Azure/azure-rest-api-specs/pull/30862 Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants