[functionapp] Block unsupported .NET 10 on Linux Consumption (Y1) for create/config set

[Copilot]

---

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

Related command

az functionapp config set --name <app-name> --resource-group <rg> --linux-fx-version "DOTNET-ISOLATED|10.0"
az functionapp create --name <app-name> --resource-group <rg> --runtime dotnet-isolated --runtime-version 10.0 ...

• Issue summary

  • CLI accepted .NET 10 on Linux Consumption (Y1), which is unsupported and can leave apps nonfunctional.
  • This change adds client-side validation to fail fast and direct users to Flex Consumption or supported runtimes.

• Change set

  • Argument validators wired in functionapp extension
    • Added validators on:
      • functionapp config set → linux_fx_version
      • functionapp create → runtime_version
  • Plan/runtime compatibility enforcement
    • Rejects DOTNET-ISOLATED|10.* for Linux apps on Y1 Consumption plans.
    • Rejects dotnet-isolated + runtime-version 10.* for Linux Consumption create flows (including --consumption-plan-location).
  • Error contract
    • Raises a CLIError with actionable guidance to use Flex Consumption or a supported runtime.
  • Focused unit coverage
    • Added validator tests for reject/allow paths in create and config-set scenarios.

if _is_dotnet_ten_linux_fx_version(namespace.linux_fx_version) and _is_linux_consumption_plan(plan):
    raise CLIError(".NET 10 (DOTNET-ISOLATED|10.0) is not supported on Linux Consumption plans. "
                   "Use a Flex Consumption plan or choose a supported runtime version.")

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? (azdev required; see .azure-pipelines/templates/azdev_setup.yml for the install command until azdev==0.2.11b1 is on PyPI)
• 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]

️✔️Azure CLI Extensions Breaking Change Test

️✔️Non Breaking Changes

[azure-client-tools-bot-prd]

Hi Copilot,
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.

[Yong Zhang (yonzhan)]

functionapp