Block update change to labels mode

[Tratcher]

Changing revisions-mode from single to labels requires changes to the traffic section at the same time. There's a dedicated command that handles this, az containerapp revision set-mode, so I've added an error message to update and up to redirect people there.

Fixes https://msazure.visualstudio.com/Antares/_workitems/edit/33230254

---

This checklist is used to make sure that common guidelines for a pull request are followed.

Related command

az containerapp update --revisions-mode
az containerapp up --revisions-mode

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
• My extension version conforms to the Extension version schema

[azure-client-tools-bot-prd]

️✔️Azure CLI Extensions Breaking Change Test

️✔️Non Breaking Changes

[azure-client-tools-bot-prd]

Hi @Tratcher,
Please write the description of changes which can be perceived by customers into HISTORY.rst.
If you want to release a new extension version, please update the version in setup.py as well.

[yonzhan]

Thank you for your contribution! We will review the pull request and get back to you soon.

[github-actions]

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).
After that please run the following commands to enable git hooks:

pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>

[Copilot]

Pull Request Overview

This PR prevents changing the Container Apps revisions mode to labels via az containerapp update or az containerapp up, and instead directs users to the dedicated az containerapp revision set-mode command.

• Block mode-switch logic in the decorator for labels mode
• End-to-end tests for both update and up commands expecting the new error
• HISTORY updated to note the disallowed change

Reviewed Changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated no comments.

File	Description
src/containerapp/azext_containerapp/tests/latest/test_containerapp_commands.py	Added test_containerapp_update_mode_e2e to assert an error is thrown when using --revisions-mode labels with update/up
src/containerapp/azext_containerapp/containerapp_decorator.py	Introduced a guard that checks for existing labels mode and raises an error directing users to revision set-mode
src/containerapp/HISTORY.rst	Documented the disallowed --revisions-mode labels change in the upcoming release notes

Comments suppressed due to low confidence (5)

src/containerapp/azext_containerapp/tests/latest/test_containerapp_commands.py:1692

• [nitpick] The test name implies only update but also covers up. Consider renaming to test_containerapp_update_and_up_labels_mode_e2e for clarity.

    def test_containerapp_update_mode_e2e(self, resource_group):

src/containerapp/azext_containerapp/tests/latest/test_containerapp_commands.py:1709

• The test checks only the generic error text. It should also assert that the message includes the recommendation to use az containerapp revision set-mode to ensure the guidance is accurate.

            self.assertIn("is not in labels mode", str(e))

src/containerapp/azext_containerapp/containerapp_decorator.py:454

• [nitpick] The comment refers to "Set-Mode" generically. For consistency, update it to reference the full az containerapp revision set-mode command.

                # Check if the app was previously in labels mode. If not, throw an error saying to use Set-Mode instead.

src/containerapp/HISTORY.rst:9

• [nitpick] In RST, command names are usually enclosed in double backticks. Consider changing * 'az containerapp update': ... to * az containerapp update: ... for consistency.

* 'az containerapp update': Disallow changing --revisions-mode to Labels.

src/containerapp/HISTORY.rst:10

• [nitpick] Similarly, wrap az containerapp up in double backticks to match project conventions: * az containerapp up: ....

* 'az containerapp up': Disallow changing --revisions-mode to Labels.

[github-actions]

Hi @Tratcher

Release Suggestions

Module: containerapp

• Update VERSION to 1.2.0b4 in src/containerapp/setup.py

Notes

• For more info about extension versioning, please refer to Extension version schema

[github-actions]

CodeGen Tools Feedback Collection

Thank you for using our CodeGen tool. We value your feedback, and we would like to know how we can improve our product. Please take a few minutes to fill our codegen survey

[zhoxing-ms]

Please take a look at this comment #8927 (comment)

[Tratcher]

@zhoxing-ms what about it? There's already an entry in History and we're not planning a new release yet.

[yanzhudd]

+@Greedygre could you please review this PR as well?

[Juliehzl]

later we can remove "labels" value for "containerapp update" and "up" command.

[Tratcher]

Good point, I had added activeRevisionsMode to up and update before I knew about set-mode, but we could remove them. The tricky part for up is that we do want to be able to create an app in labels mode.
In theory we could replicate the logic from set-mode here, but I'd rather not, switching modes is not a common operation.

[Greedygre]

Hi @Juliehzl
Please take a look, thanks