-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Release Microsoft.Network API Version 2025-05-01 #39468
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
Conversation
Copied the files in a separate commit. This allows reviewers to easily diff subsequent changes against the previous spec.
Updated the API version from stable/2025-03-01 to stable/2025-05-01.
Co-authored-by: Santosh Lokarapu <[email protected]>
* Sgw change * ModelFix * Model issue fix * Fix * Model fix * Fixed comment * Updated description for zone
* 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 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]>
…into kamboj-prjwl/release-network-2025-05-01 Sync branch with main
* Lint error fix * Response Change
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
|
|
Swagger Avocado violations for resources vmssNetworkInterface.json and vmssPublicIpAddress.json. These are the Microsoft.Compute resources and their version can't be updated to match Microsoft.Network version. |
|
Approved Avocado based on already approved in PR raised on release branch |
|
Approving the PR as the commits are already approved on release branch (release branch PR #39391) |
|
Approving suppression based on PR #39221 |
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!
This PR is combination of Multiple Networking Partner PR, which is already approved by ARM reviewer beforehand.
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.