-
Notifications
You must be signed in to change notification settings - Fork 3.3k
[Backup] BugFix: Enabled Alternate Location Restore for SQL/SAPHANA protected items #16997
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
[Backup] BugFix: Enabled Alternate Location Restore for SQL/SAPHANA protected items #16997
Conversation
|
hi @qwordy could you pls help to review? thanks |
| target_item = show_protectable_instance(cmd, protectable_items_client, resource_group_name, vault_name, | ||
| target_server_name, target_server_type, | ||
| workload_type, container_name) | ||
| if target_container_name is None: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the change is ok, while code could be refined.
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
Code owner review required |
|
Hi @fengzhou-msft could you please review this PR? |
|
Hi @fengzhou-msft i've resolved your comment. please restart the azure pipelines and approve. Thanks |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
Description
Enabled Alternate Location Restore for SQL/SAPHANA protected items
Testing Guide
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 feature.
This 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.