-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Update Restore-AzRecoveryServicesBackupItem to support NoZone as a valid TargetZone. #27010
base: main
Are you sure you want to change the base?
Update Restore-AzRecoveryServicesBackupItem to support NoZone as a valid TargetZone. #27010
Conversation
️✔️Az.Accounts
️✔️Az.Compute
️✔️Az.Network
❌Az.RecoveryServices
|
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
To the author of the pull request, |
|
|
Description
Updated Restore-AzRecoveryServicesBackupItem to support NoZone as a valid TargetZone and restricted the input for TargetZoneNumber to 1, 2, 3, and NoZone.
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.md
and reviewed the following information:ChangeLog.md
file(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
.## Upcoming Release
header in the past tense.ChangeLog.md
if no new release is required, such as fixing test case only.