Support identity in session update command

[najian]

---

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

Related command

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

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

[azure-client-tools-bot-prd]

Validation for Breaking Change Starting...

Thanks for your contribution!

[azure-client-tools-bot-prd]

Hi @najian,
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 adds support for managed identity in the az containerapp sessionpool update command by introducing new parameters and handling logic for system- and user-assigned identities, as well as registry identity.

• Extend update_session_pool signature to accept identity-related flags.
• Implement set_up_managed_identity and set_up_managed_identity_settings in the session pool decorator.
• Update registry auth configuration to allow --registry-identity and reflect it in change detection.

Reviewed Changes

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

File	Description
src/containerapp/azext_containerapp/custom.py	Updated update_session_pool signature to include identity flags.
src/containerapp/azext_containerapp/containerapp_sessionpool_decorator.py	Added managed identity setup methods; enhanced registry auth logic.

Comments suppressed due to low confidence (3)

src/containerapp/azext_containerapp/custom.py:3133

• The parameter name mi_user_assigned is inconsistent with get_argument_user_assigned. Rename it to user_assigned to align with the argument parser and decorator methods.

mi_user_assigned=None,

src/containerapp/azext_containerapp/custom.py:3135

• The parameter mi_system_assigned should be renamed to system_assigned to match get_argument_system_assigned and maintain consistency with other flags.

mi_system_assigned=False):

src/containerapp/azext_containerapp/containerapp_sessionpool_decorator.py:550

• [nitpick] Consider clarifying this error message to explicitly list the required flags (--registry-server, --registry-username, --registry-password, --registry-identity) and provide an example of using --registry-identity for MSI scenarios.

Please provide --registry-server, --registry-username, --registry-password or --registry-identity to update the registry credentials. \n

[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

[github-actions]

Hi @najian

Release Suggestions

Module: containerapp

• Update VERSION to 1.1.0b6 in src/containerapp/setup.py

Notes

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

[zhoxing-ms]

What is the difference between parameters --registry-identity with --mi-system-assigned and --mi-user-assigned?

[najian]

--registry-identity is for pull-image from ACR registry
--mi-system-assigned and --mi-user-assigned are used by container, to call other azure service
In API view, --mi-system-assigned and --mi-user-assigned need set to managedIdentity lifecycle.
--registry-identity is inside the registry credentials

[zhoxing-ms]

Got it, thanks