[Az.RecoveryServices.Backup] Fix AFS Restore Command Bug
Description
Implementing fix to handle cases where the source storage account is deleted & required sourceResourceId property is missing for restore request payload.
Tested restore where AFS source storage account was deleted before changes were made to reproduce bug. Tested restore where AFS source storage account was deleted after changes were made to validate fix.
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.)
- [X] General release
- [ ] Public preview
- [ ] Private preview
- [ ] Engineering build
- [ ] No need for a release
-
[X] Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.mdand reviewed the following information:
-
SHOULD update
ChangeLog.mdfile(s) appropriately- Update
src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.- A snippet outlining the change(s) made in the PR should be written under the
## Upcoming Releaseheader in the past tense.
- A snippet outlining the change(s) made in the PR should be written under the
- Should not change
ChangeLog.mdif no new release is required, such as fixing test case only.
- Update
- SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
- SHOULD have proper test coverage for changes in pull request.
- SHOULD NOT adjust version of module manually in pull request
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).
Hi @IannGeorges please also sync main branch in next commit to keep the changelog updated.
This PR was labeled "needs-revision" because it has unresolved review comments or CI failures. Please resolve all open review comments and make sure all CI checks are green. Refer to our guide to troubleshoot common CI failures.
@YanaXu @NoriZC can one of you please retrigger the pipeline?
/azp run
Azure Pipelines successfully started running 3 pipeline(s).
@IannGeorges we've workaround the issue with pipeline triggers - feel free to continue dev work on this PR. Thanks
/azp run
Azure Pipelines successfully started running 3 pipeline(s).
@IannGeorges There are still errors in the pipeline, please have a look!