Repository navigation
The latest Azure CLI release (2.89.1) still generates the parent Application Gateway GET command with API version 2024-10-01 #33981
Description
Activity
- addedbugThis issue requires a change to an existing behavior in the product in order to be resolved.This issue requires a change to an existing behavior in the product in order to be resolved.
on Aug 25, 2026 - addedNetworkaz network vnet/lb/nic/dns/etc...az network vnet/lb/nic/dns/etc...
on Aug 25, 2026 - addedAuto-AssignAuto assign by botAuto assign by botAzure CLI TeamThe command of the issue is owned by Azure CLI teamThe command of the issue is owned by Azure CLI teamquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
on Aug 25, 2026 Thank you for opening this issue, we will look into it.
x-engineering-agent commented
on Aug 25, 2026 ContributorMore actionsBug Analysis
az network application-gateway show(and likely the generated parent
create/update operations) issue their GET/PUT requests against API version
2024-10-01, while the sibling SSL-certificate command group
(az network application-gateway ssl-cert ..., added in #33263) correctly
uses2025-07-01, the minimum version that returns/accepts the Managed HSM
hsm.keyId/hsm.publicCertDataproperties on
sslCertificates[].properties.Because the parent resource is generated from an older AAZ command model
version, retrieving the full Application Gateway through the parentshow
(and any parent create/update read-modify-write flow) can omit or drop the
Managed HSM SSL certificate fields even though the certificate-level commands
already handle them.Affected generated sources (regenerate rather than hand-edit; the durable
source lives inAzure/aaz):src/azure-cli/azure/cli/command_modules/network/aaz/latest/network/application_gateway/_show.py
(_aaz_info["version"] = "2024-10-01")src/azure-cli/azure/cli/command_modules/network/aaz/latest/network/application_gateway/_create.py/
_update.py(and any other parent-resource operations) if they use the
same stale version.
Related command
az network application-gateway showFix
Regenerate/bump the parentapplication_gatewayAAZ command-model
operations (show, and create/update if affected) to API version
2025-07-01(or later) so the response/request schema includes the Managed
HSM SSL certificate fields, matching thessl_certsub-group. Confirm the
read-modify-write path for create/update does not drop or overwrite
sslCertificates[].properties.hsm.*when round-tripping through the parent
model.Testing Guide
- Add/extend regression coverage (recording or unit test) asserting the
parent GET request uses API version2025-07-01+ and that
sslCertificates[].properties.hsm.keyId/
hsm.publicCertDatasurvive ashowcall when the certificate is
Managed-HSM backed. - Verify a create/update round trip does not clear the HSM-backed
certificate properties.
Use this EXACT PR title:
[Network] Fix #33981:az network application-gateway show: Bump parent Application Gateway API version to 2025-07-01 so Managed HSM SSL certificate fields are preservedPR title & description format (required)
This repo enforces a PR format (guide). Please author the PR exactly as follows or CI's Check the Format of Pull Request Title and Content will fail.
Use this EXACT PR title (copy verbatim, do not reword):
[Network] Fix #33981: `az network application-gateway show`: Bump parent Application Gateway API version to 2025-07-01 so Managed HSM SSL certificate fields are preservedKeep the backticks around the command and the
Fix #33981:prefix. You may only adjust the wording after the command (the final summary) if the fix changes; the[Network]prefix, issue link, and backticked command must stay.Description — follow the PR template and fill in:
- Link the issue — start the Description with a closing keyword so the PR auto-links and closes it:
Fixes #33981. - Related command — the
az ...command this affects. - Description (mandatory) — why the bug happens, what you changed, and the resulting behavior.
- Testing Guide — example command(s) showing the fix works.
- History Notes — leave the title to drive the history note, or add extra lines in the same format (component in brackets + the command in backticks), e.g.
[Network] `az <command>`: <note>. - Keep the template checklist and tick the items you've satisfied.
x-engineering-agent commented
on Aug 25, 2026 ContributorMore actionsStarted a Copilot task in
a0x1ab/azure-cliusingclaude-sonnet-4.6: https://github.com/a0x1ab/azure-cli/tasks/04b50bda-d5f0-49ea-952e-aebf09867f26- removedbugThis issue requires a change to an existing behavior in the product in order to be resolved.This issue requires a change to an existing behavior in the product in order to be resolved.
on Aug 25, 2026 - added a commit that references this issue
on Aug 25, 2026 the pr from agent doesn't touch codegen -> not valid.
srijanee
az network application-gateway ssl-cert show -his supposed to be work, correct?the current fix is insufficient. all interfaces involving
sslCertificatesneed to be upgraded, and test cases should be added to cover the following scenario,az network application-gateway http-listener create --resource-group <> --gateway-name <> --name <> --frontend-ip <> --frontend-port <> --ssl-cert <> --host-name <>
- added a commit that references this issue
on Sep 3, 2026 - added a commit that references this issue
on Sep 7, 2026
Describe the bug
az network application-gateway showManaged HSM support for Application Gateway SSL certificates was added in API version
2025-07-01and implemented for the SSL certificate command group under #33263. The SSL certificate commands correctly use2025-07-01, but the parent Application Gateway GET remains pinned to2024-10-01.As a result, retrieving the complete Application Gateway resource through the parent
showcommand can omit the Managed HSM properties undersslCertificates[].properties.hsm.HSM PR: #33263
Related command
Errors
There is no CLI exception. The problem is the API version selected for the parent GET request and the resulting response shape.
2024-10-01ApplicationGatewayManagedHsm:2025-07-01Issue script & Debug output
The sanitized parent GET request shown by
--debuguses:The generated AAZ source in release
azure-cli-2.89.1confirms the mismatch:src/azure-cli/azure/cli/command_modules/network/aaz/latest/network/application_gateway/_show.py_aaz_info["version"] = "2024-10-01"ApplicationGatewaysGetuses2024-10-01src/azure-cli/azure/cli/command_modules/network/aaz/latest/network/application_gateway/ssl_cert/_show.py_aaz_info["version"] = "2025-07-01"hsm.keyIdandhsm.publicCertDataThe same parent/child API-version mismatch exists for generated Application Gateway create/update versus SSL certificate create/update. Those operations should also be assessed for read-modify-write behavior that could omit HSM properties.
Expected behavior
az network application-gateway showshould use an API version that supports Managed HSM, at minimum2025-07-01, and return these fields when configured:Please also verify that parent Application Gateway create/update operations cannot omit or overwrite Managed HSM SSL certificate properties because they use the older API version.
Regression coverage should verify:
Environment Summary
azure-cli 2.89.1
Additional context
No response