-
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
AKS: Get VM SKU details from backend for validation for Azure Container Storage #8178
AKS: Get VM SKU details from backend for validation for Azure Container Storage #8178
Conversation
️✔️Azure CLI Extensions Breaking Change Test
|
Hi @mukhoakash, |
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
…into mukhoakash/update_vm_sku_lookup
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.
Is there any existing test case could help validate the change? If so, please queue live test pipeline to help validate, otherwise, please add a new one.
Please fix failed CI checks (both test cases and style check). |
4e6fe67
to
b61910a
Compare
Queued live tests. |
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
2e0cdbe
to
6b72975
Compare
6b72975
to
dcbf0ed
Compare
[Release] Update index.json for extension [ aks-preview ] : https://dev.azure.com/azclitools/release/_build/results?buildId=201329&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 azdev
required)python scripts/ci/test_index.py -q
locally? (pip install wheel==0.30.0
required)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
.