[AKS] Fix for 'approuting update' command

[Suneha Bose (bosesuneha)]

---

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

Fix issue #27940.

Related command

az aks approuting update -g -n --enable-kv --attach-kv ${KEYVAULTID}

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]

️✔️Azure CLI Extensions Breaking Change Test

️✔️Non Breaking Changes

[azure-client-tools-bot-prd]

Hi Suneha Bose (@bosesuneha),
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)]

AKS

[FumingZhang]

Please also add a live test case about updating app routing configs (using custom key vault) on a cluster with monitoring addon enabled.

[FumingZhang]

lgtm

[FumingZhang]

Queued live test to validate the change, test passed!

[FumingZhang]

LGTM

[Azure CLI Bot (azclibot)]

[Release] Update index.json for extension [ aks-preview ] : https://dev.azure.com/azclitools/internal/_build/results?buildId=125945&view=results