`postgres flexible-server firewall-rule` change not included in v2.86.0

[askingcat]

Describe the bug

Four months ago, it was announced that the parameters for creating a firewall rule will change in a breaking manner with v2.86.0. This is also still stated in the docs.

However, v2.86.0 will fail if the new argument --server-name is given and the code, which I assume should have been updated, had no changes in the past four months.

Was this change potentially also postponed to v2.87.0, as many other postgres related changes?

Related command

az postgres flexible-server firewall-rule create

Errors

unrecognized arguments: --server-name ******

Issue script & Debug output

az postgres flexible-server firewall-rule create \
        --resource-group "${azname}" \
        --name "askingcat" \
        --server-name "${azname}" \
        --start-ip-address "${ip}" \
        --end-ip-address "${ip}"
unrecognized arguments: --server-name ******

(Debug log should not be necessary for this.)

Expected behavior

The new parameter(s) are recognized as announced in the documentation for breaking changes.

Environment Summary

azure-cli                         2.86.0

core                              2.86.0
telemetry                          1.1.0

Extensions:
account                            0.2.5
aks-preview                     20.0.0b6
application-insights               1.2.3
azure-devops                       1.0.3
dataprotection                     1.9.0
log-analytics                    1.0.0b1
https://aka.ms/cli_ref
Read more about the command in reference docs
resource-graph                     2.1.1

Dependencies:
msal                              1.35.1
azure-mgmt-resource               24.0.0

Python (Linux) 3.13.13 (main, May  1 2026, 00:24:40) [GCC 13.3.0]

Legal docs and information: aka.ms/AzureCliLegal


Your CLI is up-to-date

Additional context

We provided a wrapper for our users to avoid breaking changes for them by either calling az with the old parameters or the new ones, based on their version. Unfortunately, due to this bug this now didn't work as expected.

[yonzhan]

Thank you for opening this issue, we will look into it.

[a0x1ab]

🤖 AI Agent — This comment was posted automatically by the Copilot squad agent.

🔍 Bug Analysis — az postgres flexible-server firewall-rule create unrecognized --server-name

Issue: The breaking change for postgres flexible-server firewall-rule (replacing positional --server-name parameter) was announced for v2.86.0 but was not included in that release. The --server-name argument is not recognized in v2.86.0.

Affected command: az postgres flexible-server firewall-rule create

Module path: src/azure-cli/azure/cli/command_modules/rdbms/

Expected fix: Add/expose the --server-name parameter to the firewall-rule commands in the postgres flexible-server module so it matches the announced breaking-change contract.

Steps to reproduce:

az postgres flexible-server firewall-rule create   --resource-group myRG   --name myrule   --server-name myserver   --start-ip-address 1.2.3.4   --end-ip-address 1.2.3.4
# Error: unrecognized arguments: --server-name

Assigning @Copilot to investigate and implement the fix.

[a0x1ab]

🤖 AI Agent — Automated pipeline comment. Do not manually merge until tests pass.

---

🔧 Fixer: Context for Issue #33333

Issue summary: az postgres flexible-server firewall-rule commands were not updated to accept --server-name in v2.86.0 as announced in the breaking change docs.

Affected commands: create, show, update, delete, list

Expected behavior after fix:

• --server-name / -s → identifies the PostgreSQL Flexible Server
• --name / -n → identifies the firewall rule (previously --rule-name / -r)
• --rule-name / -r should no longer be valid

Linked PR: #33335 (Copilot-authored)

Next step: Tester will spin up a fresh VM, install the PR branch, and verify argument wiring. ✅

[nachoalonsoportillo]

@askingcat Thanks for raising this to our attention. Next breaking change release is June's (2.87.0). So, only then the announced breaking change will become effective. Sorry for the inconvenience this may have caused.