-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Service Gateway Swagger changes #39221
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
Service Gateway Swagger changes #39221
Conversation
Next Steps to Merge✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge.Comment generated by summarize-checks workflow run. |
API Change CheckAPIView identified API level changes in this PR and created the following API reviews
|
|
Please fix Swagger ModelValidation and place it back in queue for review. |
Updated. Please reveiw. |
| reason: False alarm. | ||
| - code: PutRequestResponseSchemeArm | ||
| from: serviceGateway.json | ||
| reason: Code issue in PutRequestResponseSchemeArm validation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is code issue on API spec side Azure/azure-openapi-validator#752. Once issue is resolved , we don't need suppression.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated reason a bit and we need this suppression for whole file, until there is fix.
specification/network/resource-manager/Microsoft.Network/stable/2025-05-01/serviceGateway.json
Outdated
Show resolved
Hide resolved
| "items": { | ||
| "type": "string" | ||
| }, | ||
| "description": "A list of availability zones denoting the zone in which service gateway should be deployed." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don’t specify zone formats in definitions for other resources either, so we’re using the same description used for NAT Gateway and Load Balancer.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is a good opportunity to update those descriptions as well
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated description for zone for service gateway.
specification/network/resource-manager/Microsoft.Network/stable/2025-05-01/serviceGateway.json
Show resolved
Hide resolved
specification/network/resource-manager/Microsoft.Network/stable/2025-05-01/serviceGateway.json
Outdated
Show resolved
Hide resolved
specification/network/resource-manager/Microsoft.Network/stable/2025-05-01/serviceGateway.json
Show resolved
Hide resolved
ef68004
into
release-microsoft-network-2025-05-01
* Copy files from stable/2025-03-01 Copied the files in a separate commit. This allows reviewers to easily diff subsequent changes against the previous spec. * Update version to stable/2025-05-01 Updated the API version from stable/2025-03-01 to stable/2025-05-01. * Added tag for 2025-05-01 in readme file * Update Suppression and directives from previous verison * Update version to stable 2025-05-01 (#39294) Co-authored-by: Santosh Lokarapu <[email protected]> * Service Gateway Swagger changes (#39221) * Sgw change * ModelFix * Model issue fix * Fix * Model fix * Fixed comment * Updated description for zone * Azure Firewall Policy: Add New IDPS Profiles (#36855) * Update IDPS Profile names * Add examples for IDPS profile * Update Firewall Policy PUT example IDPS profile * Update profile name and enum order * Remove delete example * Update profile names to emerging, extended and core * Add Off as default profile * Move changes to latest release * Revert PUT example change on older version * Move changes to release 2025-05-01 * Update examples release version * Update profile order * Update profiles description * Add vna top level resource 2025-05-01 (#39341) * Add a new top level resource for VNA * add suppression for a known issue. * add 1 more suppression due to known issue * added x-ms-parameter-location as per go sdk team suggestion * one more place to add for x-ms-parameter-location attribute --------- Co-authored-by: Prajjwal Kamboj <[email protected]> * Update the AppGW WAF spec with CAPTCHA action and Cookie expiary (#39362) * update the spec with CAPTCHA action and cookies expiary * whitespace issue * Fix description for CAPTCHA cookie expiration * Lint error fix (#39410) * Lint error fix * Response Change --------- Co-authored-by: Prajjwal Kamboj <[email protected]> Co-authored-by: santoshgh317 <[email protected]> Co-authored-by: Santosh Lokarapu <[email protected]> Co-authored-by: anjbal <[email protected]> Co-authored-by: Saloni Rajeev Kumar <[email protected]> Co-authored-by: Arjun Patel <[email protected]> Co-authored-by: Yaniv Sagron <[email protected]>
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.PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.
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.write accessper aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositoriesNext 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.