-
Notifications
You must be signed in to change notification settings - Fork 1.5k
revert az aks copilot #6773
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
revert az aks copilot #6773
Conversation
❌Azure CLI Extensions Breaking Change Test
|
|
Hi @sulixu, |
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
| +++++++ | ||
| * Add `--disable-workload-identity` to the `az aks update` command. | ||
|
|
||
| 0.5.156 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe you should keep this version history as it has been released
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is better to keep this version and add a new version in HISTORY.rst and setup.py with the revertion info as changelog.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
It is better to add the link of feature PR in #6773 (comment) |
|
[Release] Update index.json for extension [ aks-preview ] : https://dev.azure.com/azclitools/internal/_build/results?buildId=91439&view=results |
revert commits related with az aks copilot
#6629
#6750
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?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.