-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Kamboj prjwl/release network microsoft.network 2024 05 01 #31095
base: main
Are you sure you want to change the base?
Kamboj prjwl/release network microsoft.network 2024 05 01 #31095
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/2024-03-01 to stable/2024-05-01.
* Add IPAM, VNV, update Security Admin and Vnet specs * adminrule error * adding suppressions * suppression spacing * space issue * another space update * the issue was 2024-03 readme and not 2024-05 * adding suppressions * removing location headers * reverting location header changes for delete * Update sdk-suppressions.yaml * mark networkManagerScopeAccess as an optional property * update go breaking suppressions --------- Co-authored-by: kazrael2119 <98569699+kazrael2119@users.noreply.github.com> Co-authored-by: Chenjie Shi <tadelesh.shi@live.cn>
* Swagger changes for expressroute site failover simulation * Fixing some checks * Correcting parameter name in stop json * Changing error schema * Adding arm id format for uris * Adding suppressions
* Added location headers to 202 responses for ipGroups and virtualRouters. * Added location header to vr peering delete examples * Ran prettier on 2024-05-01 examples
…workInterface (#30692) * [Network] - Adding DefaultOutboundConnectivityEnabled property in networkInterface * address prettier check
* add private only feature to azure bastion service * fix Swagger PrettierCheck * fix the swagger PrettierCheck * modify the api version * modify file name --------- Co-authored-by: Leo Liu (from Dev Box) <leoliu2@microsoft.com>
Next Steps to MergeNext steps that must be taken to merge this PR:
|
Generated ApiView
|
Azure Pipelines successfully started running 2 pipeline(s). |
@kamboj-prjwl please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
ARM (Control Plane) API Specification Update Pull Request
Tip
Overwhelmed by all this guidance? See the
Getting help
section 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 ApiView
comment 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 PR
andDue diligence checklist
.write access
per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositoriesNext Steps to Merge
comment. 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.
queued
state, please add a comment with contents/azp run
.This should result in a new comment denoting a
PR validation pipeline
has started and the checks should be updated after few minutes.