[containerapp] az containerapp [create/update] --environment-mode WorkloadProfiles Add environment mode to az containerapp

[jepetty]

---

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

Related command

az containerapp env create --name --resource-group --environment-mode WorkloadProfiles
az containerapp env update --name --resource-group --environment-mode WorkloadProfiles

Why this change over the existing --enable-workload-profiles switch?
The Azure Container Apps team is experimenting with new environment types beyond just ConsumptionOnly and Dedicated/Consumption leveraging new technologies. This change enable us to rapidly iterate on this experimentation by easily creating new environments, as well as ensure the experience of creation through CLI is prioritized the entire time.

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

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]

⚠️Azure CLI Extensions Breaking Change Test

⚠️containerapp

rule	cmd_name	rule_message	suggest_message
⚠️ 1006 - ParaAdd	containerapp env create	cmd containerapp env create added parameter environment_mode
⚠️ 1006 - ParaAdd	containerapp env update	cmd containerapp env update added parameter environment_mode

[azure-client-tools-bot-prd]

Hi @jepetty,
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>

[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

[Greedygre]

What is the value allowed?
Recommend to use arg_type=get_enum_type(["consumptiononly"]) to make it more clear.

[Tratcher]

We don't want to constrain the type right now because we're introducing several experimental values and names may frequently change.

[Greedygre]

May I ask why do we need to add --environment-mode? Seems this change not relate to backend feature?
Is it only relate to CLI behavior?

az containerapp env create --name --resource-group --environment-mode WorkloadProfiles
az containerapp env update --name --resource-group --environment-mode WorkloadProfiles

We already have -w, what is the difference?:

 --enable-workload-profiles -w                                         : Boolean indicating if
                                                                            the environment is
                                                                            enabled to have workload
                                                                            profiles.  Allowed
                                                                            values: false, true.
                                                                            Default: True.

[Greedygre]

May I ask why do we need to add --environment-mode? Seems this change not relate to backend feature? Is it only relate to CLI behavior?

az containerapp env create --name --resource-group --environment-mode WorkloadProfiles
az containerapp env update --name --resource-group --environment-mode WorkloadProfiles

We already have -w, what is the difference?:

 --enable-workload-profiles -w                                         : Boolean indicating if
                                                                            the environment is
                                                                            enabled to have workload
                                                                            profiles.  Allowed
                                                                            values: false, true.
                                                                            Default: True.

Base on the code, the --environment-mode WorkloadProfiles equals -w, right? And --environment-mode consumptiononly equals -w false.

I think in portal, we already deprecate -w false, we cannot create consumptiononly environment from portal now.
Why you create a new params in CLI to support this? what is the business background? @jepetty

[jepetty]

May I ask why do we need to add --environment-mode? Seems this change not relate to backend feature? Is it only relate to CLI behavior?

az containerapp env create --name --resource-group --environment-mode WorkloadProfiles
az containerapp env update --name --resource-group --environment-mode WorkloadProfiles

We already have -w, what is the difference?:

 --enable-workload-profiles -w                                         : Boolean indicating if
                                                                            the environment is
                                                                            enabled to have workload
                                                                            profiles.  Allowed
                                                                            values: false, true.
                                                                            Default: True.

@Greedygre great question! Chatted a bit offline, but including here as well

We're in the process of experimenting with new environment types aside from our v1 ConsumptionOnly and v2 Dedicated/Consumption environments. We're experimenting with better experiences for our users - both in terms of speed of provisioning/environment creation and in terms of cost-savings. I do think we should consider deprecating the -w flag, and I'm happy to create an issue to perform this work, let me know what you think!

[jepetty]

Updated the PR description to provide additional background for this change - thanks for the questions, @Greedygre!