{AKS} Add backward compatibility to cli

[FumingZhang]

---

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

• Remove aks browse.
• Add support for option --edge-zone.
• Align api server access profile validation with cli.
• Backward compatibility with old api 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?

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.

[yonzhan]

AKS

[wangzelin007]

LGTM

[FumingZhang]

/azp where

[azure-pipelines]

Azure DevOps orgs getting events for this repository:

• azure-sdk

[FumingZhang]

/azp help

[azure-pipelines]

Supported commands

• help:
• Get descriptions, examples and documentation about supported commands
• Example: help "command_name"
• list:
• List all pipelines for this repository using a comment.
• Example: "list"
• run:
• Run all pipelines or specific pipelines for this repository using a comment. Use this command by itself to trigger all related pipelines, or specify specific pipelines to run.
• Example: "run" or "run pipeline_name, pipeline_name, pipeline_name"
• where:
• Report back the Azure DevOps orgs that are related to this repository and org
• Example: "where"

See additional documentation.

[FumingZhang]

/azp list

[azure-pipelines]

CI/CD Pipelines for this repository:

• Azure.azure-cli-extensions

[zhoxing-ms]

Please add descriptions of these changes in history note. If you need to upgrade extension version to release these changes, please modify setup.py at the same time

[zhoxing-ms]

@FumingZhang If deleting this command will cause breaking change to the user, please mark it as [BREAKING CHANGE] in the history notes

[FumingZhang]

Hi @zhoxing-ms, I suppose user should always have azure-cli installed before using aks-preview and if a command is not implemented in azure-cli-extensions, it will fall back to the implementation in azure-cli.

For this case, the implementation of aks browse is basically the same in azure-cli and azure-cli-extensions (actually a little bit more logic in azure-cli), and after removing this command declaration from the extension side, when aks browse is executed, the implementation in azure-cli will be used.

[FumingZhang]

Please add descriptions of these changes in history note. If you need to upgrade extension version to release these changes, please modify setup.py at the same time

As I explained above, the changes in this PR should not introduce breaking changes that users can detect. The command aks browse will fall back to the implementation in azure-cli, and the new option --edge-zone introduced to aks create is in preview and user may not use it.