Adding 2 New PS command lets for new POST APIs to fetch secrets. #28556
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. |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
…/azure-powershell into nilamd-release-network-2024-10-01
VeryEarly
requested changes
Sep 16, 2025
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
@VeryEarly Thanks for the review comments. I have incorporated review comments. Please help take a look. Thanks! |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
Commenter does not have sufficient privileges for PR 28556 in repo Azure/azure-powershell |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
…/azure-powershell into nilamd-release-network-2024-10-01
|
@VeryEarly I have pushed tests new recordings. Please take a look when you get chance. Thanks a lot! |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
Fixed credscan errors in help files. Thanks! |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
@VeryEarly Now all tests are passing. Can you help with suppressing the breaking change warning as you mentioned? Please help merge. Thanks a lot! |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
VeryEarly
approved these changes
Sep 22, 2025
VeryEarly
merged commit 76290ed
into
Azure:release-network-2024-10-01
10 of 12 checks passed
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
Adding 2 New PS command lets for new POST APIs to fetch secrets.
Adding 2 new powershell cmdlets to fetch Radius secrets set on VirtualNetworkGateway and VirtualWan VpnServerConfiguration resources.
https://github.com/Azure/azure-powershell-cmdlet-review-pr/issues/1513
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.