-
Notifications
You must be signed in to change notification settings - Fork 3.3k
{Backup} Add CRR config entries for upcoming regions northeastus5 and… #32659
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
base: dev
Are you sure you want to change the base?
Conversation
… indiasouthcentral
️✔️AzureCLI-FullTest
|
️✔️AzureCLI-BreakingChangeTest
|
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR. Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
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.
Pull request overview
This PR adds Cross-Region Restore (CRR) configuration entries for two upcoming Azure regions: northeastus5 and indiasouthcentral. These entries enable Azure Backup to support cross-region restore functionality by mapping each new region to its designated secondary region for disaster recovery purposes.
Changes:
- Added mapping for
indiasouthcentralregion with secondary regioncentralindia - Added mapping for
northeastus5region with secondary regioncentralus
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
… indiasouthcentral
Related command
az backup
Description
This PR adds important config to enable Cross Region Support for Azure Backup for upcoming regions
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.