-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Added 'aks nodepool snapshot update' command #6433
Conversation
Updates tags on a nodepool snapshot matching updated behavior!
Hi @pineapplethevoyager, |
Thank you for your contribution! We will review the pull request and get back to you soon. |
...iew/azext_aks_preview/tests/latest/recordings/test_aks_create_with_auto_upgrade_channel.yaml
Outdated
Show resolved
Hide resolved
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.
Please resolve merge conflicts
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
Co-authored-by: Yan Zhu <[email protected]>
Co-authored-by: Yan Zhu <[email protected]>
This reverts commit 143a6cd.
This reverts commit abb15e6.
The build fail seems common with other pipelines (Pipelines - Run 20230630.20). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Co-authored-by: Xing Zhou <[email protected]>
[Release] Update index.json for extension [ aks-preview ] : https://dev.azure.com/azclitools/internal/_build/results?buildId=70238&view=results |
Updates tags on a nodepool snapshot matching updated behavior!
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 azdev
required)python scripts/ci/test_index.py -q
locally?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.json
automatically.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
.