[Containerapp] az containerapp function: Add function key management commands

[khushishah513]

---

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 @khushishah513,
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

[krishnajaju]

please review these commands from Nitesh/Deep as well.

[krishnajaju]

we also have master key and system keys. Instead of adding separate commands for each type of keys, can we follow the same approach as that of az functionapp keys and az functionapp function keys

My suggestion is to have only one command that handles all kinds of function keys, following the az functionapp conventions.

az containerapp function keys list/delete/set --key-type {functionKeys, hostKey, masterKey, systemKeys} [--function-name] {} [--key-name] {} [--key-value] {}

• if keyType is functionKeys, --function-name becomes mandatory parameter, else it is optional.
• keyType is mandatory parameter
• list --> to view all keys with given keyType
• delete --> delete a key with given keyType and keyName (keyName required only when keyType is functionKeys. Is it possible to delete master key, host key in case of other Functions SKUs using az functionapp keys command?
• set --> add new key or update existing key. (Only update operation supported in host and master key. Add or update supported in functionKeys)
• function-name, key-name and key-value parameters will be applicable only in certain combination of commands.

[krishnajaju]

Reference - https://learn.microsoft.com/en-us/azure/azure-functions/function-keys-how-to?tabs=azure-portal#understand-keys