[connectedk8s] Update extension CLI to v1.10.5#8454
Conversation
* ruff fix * remove duplicate code block * cleaner fix for no existing kubeconfig makes the type annotations true again
…ForKubernetes/connectedk8s into atchub/helminstallerror
…p_migration Add AT refresh for Proxy
Add Kubectl Check to Proxy Test
…ForKubernetes/connectedk8s into atchub/helminstallerror
…rror add telemetry for helm install error
️✔️Azure CLI Extensions Breaking Change Test
|
|
Hi @bavneetsingh16, |
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
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). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
|
|
We have set up live tests in our forked repository as a continuous integration (CI) check and those tests include coverage for all these changes. All the tests can be found here: https://github.com/AzureArcForKubernetes/connectedk8s/blob/main/testing/test/configurations As the code owners of this extension CLI, we mandate that all changes be first made in our forked repository to ensure they undergo our comprehensive test suite |
|
[Release] Update index.json for extension [ connectedk8s-1.10.5 ] : https://dev.azure.com/msazure/One/_build/results?buildId=114449774&view=results |
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
General Guidelines
azdev style <YOUR_EXT>locally? (pip install azdevrequired)python scripts/ci/test_index.py -qlocally? (pip install wheel==0.30.0required)For new extensions:
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.jsonautomatically.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.