Update azure Policy key under addonProfiles matching Azure Portal casing

[nirnaymsft]

When user enable policy via Portal the key added to addonProfiles is azurePolicy. Matching name in CLI as well.

---

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

Related command

az aks enable-addons
az aks addon list

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

[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]

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

[FumingZhang]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[FumingZhang]

@nirnaymsft, may I ask what's the motivation to update the value? cc @fseldow

[nirnaymsft]

@nirnaymsft, may I ask what's the motivation to update the value? cc @fseldow

This is customer raised issue. The RCA showed that, Enabling Azure Policy via CLI and Portal is causing different behavior in name of azurepolicy under addonProfiles object.

[nirnaymsft]

/azp run

[azure-pipelines]

Commenter does not have sufficient privileges for PR 8495 in repo Azure/azure-cli-extensions

[yonzhan]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[fseldow]

/lgtm

[robbiezhang]

you can revert this change now.

[FumingZhang]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[FumingZhang]

lgtm

but I have a question about if the goal is to fix the case issue in command az aks enable-addons and az aks addon enable only, user could also enable the policy addon when creating the cluster, do you want to fix the issue in that command too?

[FumingZhang]

There are some existing test cases that create the AKS cluster with policy addon enabled, maybe you can modify one of those case to validate the change?