[AKS] Add auto upgrade channel to aks create and update

[xhl873]

---

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

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?

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 PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

[azuresdkci]

If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:

docker run -it mcr.microsoft.com/azure-cli:latest
export EXT=<NAME>
pip install --upgrade --target ~/.azure/cliextensions/$EXT "git+https://github.com/xhl873/azure-cli-extensions.git@xhl/upgradechannel2#subdirectory=src/$EXT&egg=$EXT"

[yonzhan]

AKS

[charliedmcb]

Looks good to me. Although, I don't know the area well enough to say with certainty :)

There are also a few failing checks that need to be resolved.

[xhl873]

Looks good to me. Although, I don't know the area well enough to say with certainty :)

There are also a few failing checks that need to be resolved.

yea, I am aware of the failures, waiting for Bo's PR to vendor 11-01 API, and there are a couple of test fixes also. I need to merge once that change is in (I have vendored that locally for testing purpose.)

[arrownj]

Is there a possibility to add test for this new parameter ?

[arrownj]

Are these values defined in the swagger and have been defined as Enum in the SDK ? If yes, we may be able to leverage it instead of defining separately.

[xhl873]

they are defined in the swagger, however, consts file does depend on the versioned SDK, not sure if it's the reason that we are defining these consts here (don't want to introduce dependency?). Probably I am going to break the pattern and keep it consistent for now. :)

[xhl873]

Is there a possibility to add test for this new parameter ?

yes, I've added a test (and recording), please take a look

[paulgmiller]

/azp run

[azure-pipelines]

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

[yungezz]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).