[Network] az network vnet-gateway: Support VNET Gateway failover#31986
Merged
[Network] az network vnet-gateway: Support VNET Gateway failover#31986
az network vnet-gateway: Support VNET Gateway failover#31986Conversation
Shubhika-1795
requested review from
jsntcy,
kairu-ms,
necusjz and
wangzelin007
as code owners
️✔️AzureCLI-FullTest
|
Collaborator
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
Hi @Shubhika-1795, |
|
The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR. Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
|
| rule | cmd_name | rule_message | suggest_message |
|---|---|---|---|
| network vnet-gateway get-failover-all-tests-detail | cmd network vnet-gateway get-failover-all-tests-detail added |
||
| network vnet-gateway get-failover-single-test-detail | cmd network vnet-gateway get-failover-single-test-detail added |
||
| network vnet-gateway start-site-failover-test | cmd network vnet-gateway start-site-failover-test added |
||
| network vnet-gateway stop-site-failover-test | cmd network vnet-gateway stop-site-failover-test added |
microsoft-github-policy-service
bot
added
the
customer-reported
Contributor
|
Thank you for your contribution @Shubhika-1795! We will review the pull request and get back to you soon. |
Shubhika-1795
changed the title
az network vnet-gateway: Adding azure cli commands for 4 new VNET Gateway Failover APIs
Shubhika-1795
changed the title
az network vnet-gateway: Adding azure cli commands for 4 new VNET Gateway Failover APIsaz network vnet-gateway: Add support for 4 new VNET Gateway Failover APIs
necusjz
changed the title
az network vnet-gateway: Add support for 4 new VNET Gateway Failover APIsaz network vnet-gateway: Support VNET Gateway failover
Member
|
/azp run |
necusjz
approved these changes
Aug 26, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related command
Description
Adding 4 new APIs -
Testing Guide
help output for all APIs -
History Notes
[Component Name 1] BREAKING CHANGE:
az command a: Make some customer-facing breaking change[Component Name 2]
az command b: Add some customer-facing featureThis checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.
Testing Guide
help output for all APIs -
History Notes
[Component Name 1] BREAKING CHANGE:
az command a: Make some customer-facing breaking change[Component Name 2]
az command b: Add some customer-facing featureThis checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.