Conversation
️✔️AzureCLI-FullTest
|
|
| rule | cmd_name | rule_message | suggest_message |
|---|---|---|---|
| postgres flexible-server create | cmd postgres flexible-server create added parameter allow_same_zone |
||
| postgres flexible-server create | cmd postgres flexible-server create added parameter zonal_resiliency |
||
| postgres flexible-server update | cmd postgres flexible-server update added parameter allow_same_zone |
||
| postgres flexible-server update | cmd postgres flexible-server update added parameter zonal_resiliency |
|
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.
Pull request overview
This PR introduces a new user-facing experience for configuring high availability in PostgreSQL flexible servers by adding --zonal-resiliency and --allow-same-zone arguments while deprecating the existing --high-availability parameter. The change aligns the CLI with the Azure Portal's Multi-Availability Zone (MAZ) experience.
Key Changes:
- New
--zonal-resiliencyparameter (Enabled/Disabled) replaces--high-availability(ZoneRedundant/SameZone/Disabled) - New
--allow-same-zoneflag permits primary and standby instances in the same zone when multi-zone capacity is limited - Mutual exclusivity validation prevents using both old and new parameters together
Reviewed changes
Copilot reviewed 6 out of 7 changed files in this pull request and generated 6 comments.
Show a summary per file
| File | Description |
|---|---|
validators.py |
Adds validation logic for new zonal resiliency parameters, including mutual exclusivity checks and single-AZ region handling |
flexible_server_custom_postgres.py |
Updates create and update functions to handle new parameters and derive high availability mode from zonal resiliency settings |
_params.py |
Defines new argument types for --zonal-resiliency and --allow-same-zone in both create and update commands |
_helptext_pg.py |
Adds example demonstrating usage of new --zonal-resiliency and --allow-same-zone parameters |
_breaking_change.py |
Registers deprecation for --high-availability parameter (new file) |
test_rdbms_flexible_commands.py |
Updates test to use new --zonal-resiliency parameter instead of deprecated --high-availability |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review for a chance to win a $100 gift card. Take the survey.
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
@evelyn-ys please run checks. |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
@evelyn-ys checks please merge |
Related command
az postgres flexible-server create/updateDescription
Use of
--zonal-resiliencycommand to better align to portal MAZ experience. Primary and standby instances are placed in separate zones for better availability. If zonal capacity is limited, you can allow both in the same zone by checking the box.This also introduces the deprecation of
--high-availabilityTesting Guide
az postgres flexible-server create --zonal-resiliency Enabled --high-availability SameZone --allow-same-zone -g nasc-livesite -n nasctest-121-4093 --location eastus
Argument '--high-availability' has been deprecated and will be removed in next breaking change release(2.86.0) scheduled for May 2026. Use '--zonal-resiliency' instead.
Checking the existence of the resource group 'nasc-livesite'...
Resource group 'nasc-livesite' exists ? : True
Setting both --high-availability and --zonal-resiliency is not allowed. Please set only --zonal-resiliency to move forward.
History Notes
[RDBMS]
az postgres flexible-server create/update: Show high availability feature with zonal resiliency argument