[containerapp] Hardcoded API Version "2025-01-01" Causes Failures with Future System Dates

[azclibot]

Source: Azure/azure-cli#32181 (by Don Hicks (@don-hicks))
Affected extension: containerapp (src/containerapp/)

---

<<UNTRUSTED:issue-32181>>

Issue #32181 (by Don Hicks (@don-hicks))

Title

Hardcoded API Version "2025-01-01" Causes Failures with Future System Dates

Body

Describe the bug

Azure CLI containerapp module fails with "InvalidApiVersionParameter" when system date is set to 2025. The core module has a hardcoded API version "2025-01-01" that is not valid. This affects all containerapp commands when using the core module (not extension) on systems with dates in 2025.

Related command

'''
az containerapp list
az containerapp logs show
az containerapp show
'''

Errors

'''
ERROR: (InvalidApiVersionParameter) The api-version '2025-01-01' is invalid. The supported versions are '2025-04-01,2025-03-01,2024-10-01-preview,2024-11-01,2024-08-01,2024-07-01,2024-06-01-preview,2024-03-01,2023-07-01,2023-07-01-preview,2023-03-01-preview,2022-12-01,2022-11-01-preview,2022-09-01,2022-06-01,2022-05-01,2022-03-01-preview,2022-01-01,2021-04-01,2021-01-01,2020-10-01,2020-09-01,2020-08-01,2020-07-01,2020-06-01,2020-05-01,2020-01-01,2019-11-01,2019-10-01,2019-09-01,2019-08-01,2019-07-01,2019-06-01,2019-05-10,2019-05-01,2019-03-01,2018-11-01,2018-09-01,2018-08-01,2018-07-01,2018-06-01,2018-05-01,2018-02-01,2018-01-01,2017-12-01,2017-08-01,2017-06-01,2017-05-10,2017-05-01,2017-03-01,2016-09-01,2016-07-01,2016-06-01,2016-02-01,2015-11-01,2015-01-01,2014-04-01-preview,2014-04-01,2014-01-01,2013-03-01,2014-02-26,2014-04'.
'''

Issue script & Debug output

'''

Reproduction script

#!/bin/bash

Show system date (2025-09-26)

date

Ensure core module is used (not extension)

az extension remove -n containerapp 2>/dev/null

Try to list container apps

az containerapp list --resource-group "myresourcegroup" --debug 2>&1 | grep -A5 -B5 "api-version"
'''

Debug output shows:

'''
Request URL: https://management.azure.com/subscriptions/{subscription-id}/resourceGroups/myresourcegroup/providers/Microsoft.App/containerApps?api-version=2025-01-01
Response status: 400
Response headers: {...}
Response content: {"error":{"code":"InvalidApiVersionParameter","message":"The api-version '2025-01-01' is invalid..."}}
'''

Expected behavior

Commands should execute successfully using a valid API version like "2024-03-01" instead of the hardcoded "2025-01-01".

Environment Summary

'''
azure-cli 2.77.0

core 2.77.0
telemetry 1.1.0

Dependencies:
msal 1.31.0
azure-mgmt-resource 23.2.0

Python location '/opt/az/bin/python3'
Extensions directory '/home/glucose/.azure/cliextensions'

Python (Linux) 3.13.0 (main, Oct 8 2024, 01:04:00) [GCC 11.4.0]

Legal docs and information: aka.ms/AzureCliLegal
'''

Additional context

The root cause is in /opt/az/lib/python3.13/site-packages/azure/cli/command_modules/containerapp/_clients.py line 19:
''' python
CURRENT_API_VERSION = "2025-01-01"
'''

This hardcoded value is not a valid API version. The issue only affects the core module - when the containerapp extension is installed, it masks this bug.

Workaround:
''' bash
sudo sed -i 's/CURRENT_API_VERSION = "2025-01-01"/CURRENT_API_VERSION = "2024-03-01"/'
/opt/az/lib/python3.13/site-packages/azure/cli/command_modules/containerapp/_clients.py
'''

System Information:

• OS: Linux 6.6.87.2-microsoft-standard-WSL2
• System Date: 2025-09-26
• Python: 3.13

Comments

Comment by @azure-client-tools-bot-prd[bot]

Hi Don Hicks (@don-hicks),

2.64.0 is not the latest Azure CLI(2.77.0).

If you haven't already attempted to do so, please upgrade to the latest Azure CLI version by following https://learn.microsoft.com/en-us/cli/azure/update-azure-cli.

Comment by Yong Zhang (@yonzhan)

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

Comment by Don Hicks (@don-hicks)

Yes, sorry, I put the wrong version in the initial report, it is the latest 2.77 where the bug has surfaced

Comment by Greedygre (@Greedygre)

Hi Don Hicks (@don-hicks)
Did you still occur this issue?
May I ask what is the Location that you got this issue?

Comment by Greedygre (@Greedygre)

Hi Don Hicks (@don-hicks)

After investigation, we found issue cause by the command run with --resource-group/-g with empty value, repro:
'''
az containerapp list --resource-group "" --debug --query "[].name"
'''

Can you specify a valid resource group name or without --resource-group/-g in the command?

Edit:

Here is the request we found for your request
'''
https://management.azure.com:443/subscriptions/{sub-id}/resourceGroups/providers/Microsoft.App/containerApps?api-version=2025-01-01
'''
There is no myresourcegroup shown in the URL, Can you check why the resource group value didn't set correctly?

Thanks

<<END:issue-32181>>

[azclibot]

Context

This issue is tracked from Azure/azure-cli#32181.

The containerapp extension has a hardcoded CURRENT_API_VERSION = "2025-01-01" in _clients.py that is not a valid API version according to the Azure Management API. This causes all az containerapp commands to fail with InvalidApiVersionParameter when using the core containerapp module (without the extension installed).

Failing commands:

• az containerapp list
• az containerapp logs show
• az containerapp show

Error:

ERROR: (InvalidApiVersionParameter) The api-version '2025-01-01' is invalid. The supported versions are '2025-04-01,2025-03-01,2024-10-01-preview,2024-11-01,2024-08-01,2024-07-01,...'

Root cause: In src/containerapp/azext_containerapp/_clients.py (or equivalent), CURRENT_API_VERSION is set to "2025-01-01" which is not in the list of supported API versions.

Fix needed: Update CURRENT_API_VERSION to a valid supported API version such as "2024-11-01" or the latest stable version listed in the error message.

Verified environment:

• azure-cli 2.77.0
• Python 3.13.0, Linux (WSL2)

PR 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.

Title

• Start with [Container Apps] — square brackets [] for a customer-facing change (added to HISTORY.rst), curly {} if not. A bug fix is customer-facing, so use [].
• Then Fix #10018: to link the issue.
• Then optionally the affected command az <command>:.
• Then a present-tense, capitalized verb (Fix for bug fixes; Add/Change/Deprecate/Remove otherwise) and a concise summary.
• Recommended title: [Container Apps] Fix #10018: az <command>: Fix <concise description of the fix>

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 #10018.
• 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 [Container Apps] az <command>: <note> lines for extra notes.
• Keep the template checklist and tick the items you've satisfied.

---

Posted by agent-assist (autonomous bug-fix pipeline).

[yonzhan]

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