Vnet gateway failover and insights ap is #28500
Draft
Conversation
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
| Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
|
Thank you for your contribution @Shubhika-1795! We will review the pull request and get back to you soon. |
Shubhika-1795
force-pushed
the
VNET_Gateway_Failover_and_insights_APIs
branch
from
6afb1f6 to
04d73b1
Compare
VeryEarly
reviewed
Sep 4, 2025
src/Network/Network/ChangeLog.md
Outdated
| @@ -26,6 +26,12 @@ | |||
| - `Add-AzApplicationGatewayBackendHttpSetting` | |||
| - `Set-AzApplicationGatewayBackendHttpSetting` | |||
| * Onboarded Maps to Private Link Common Cmdlets | |||
| * Added cmdlet `Get-AzVirtualNetworkGatewayFailoverSingleTestDetails` to retrieve details of a single failover test on a virtual network gateway. | |||
There was a problem hiding this comment.
can you please move new change logs to line 22 right under Upcoming Release? This will help better resolve merge conflicts
VeryEarly
reviewed
Sep 4, 2025
| # Get-AzVirtualNetworkGatewayFailoverAllTestsDetails | ||
|
|
||
| ## SYNOPSIS | ||
| {{ Fill in the Synopsis }} |
There was a problem hiding this comment.
please fulfill synopsis, description and examples
VeryEarly
reviewed
Sep 4, 2025
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
done |
Shubhika-1795
changed the base branch from
release-network-2024-10-01
to
main
Shubhika-1795
changed the base branch from
main
to
release-network-2024-10-01
Shubhika-1795
changed the base branch from
release-network-2024-10-01
to
main
Shubhika-1795
changed the base branch from
main
to
release-network-2024-10-01
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Mandatory Checklist
Please choose the target release of Azure PowerShell. (⚠️ Target release is a different concept from API readiness. Please click below links for details.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.mdand reviewed the following information:ChangeLog.mdfile(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.## Upcoming Releaseheader in the past tense.ChangeLog.mdif no new release is required, such as fixing test case only.