[k8s-extension] Update extension CLI to v1.3.0

[Bavneet Singh (bavneetsingh16)]

---

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?

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.
The precondition is to put your code inside this repository and upgrade the version in the pull request but do not modify src/index.json.

[Yong Zhang (yonzhan)]

k8s-extension

[Xing Zhou (zhoxing-ms)]

Could you add some test cases for those change?

[Bavneet Singh (bavneetsingh16)]

Could you add some test cases for those change?

• Currently we test for each partner extension in our forked repository (pr creation) before requesting for merging changes upstream, unfortunately currently we cannot include provisionedClusters in our tests as they need special hardware requirements which is not supportable. It is being worked on and could be added in the future.
  pr initiated CI check - https://github.com/AzureArcForKubernetes/azure-cli-extensions/blob/k8s-extension/public/testing/pipeline/k8s-custom-pipelines.yml
  CI check for each partner extension - https://github.com/AzureArcForKubernetes/azure-cli-extensions/tree/k8s-extension/public/testing/test/extensions/public

• Also, all the extension requests for provisionedcluster works in the same way as for other cluster types, so the behavior for the extensions requests have not been changed in this pr