azure-cli-extensions
azure-cli-extensions copied to clipboard
Changing default windows image from the old 2016 to the 2022 image
This is technically a breaking change, with the messaging being sent here: Default windows image change breaking change warning, Win2016 to Win2022 by Sandido · Pull Request #8045 · Azure/azure-cli-extensions (github.com)
Update: changing the image to 2022 smalldisk instead to reduce the breaking change impact and due to a known disk id conflict issue with identical images.
This change prevents the old 2016 image from being used by default, rather to a newer method that first tries to use the source VM image, and if that cannot be found it uses the 2022 image.
This PR should be released in time for the November Ignite breaking change release.
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
General Guidelines
- [x] Have you run
azdev style <YOUR_EXT>locally? (pip install azdevrequired) - [x] Have you run
python scripts/ci/test_index.py -qlocally? (pip install wheel==0.30.0required) - [x] My extension version conforms to the Extension version schema
For new extensions:
- [x] 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.
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.
️✔️Azure CLI Extensions Breaking Change Test
️✔️Non Breaking Changes
Hi @Sandido, Please write the description of changes which can be perceived by customers into HISTORY.rst. If you want to release a new extension version, please update the version in setup.py as well.
Hi @Sandido, Since the current milestone time is less than 7 days, this pr will be reviewed in the next milestone.
Thank you for your contribution! We will review the pull request and get back to you soon.
- For more info about extension versioning, please refer to Extension version schema
This PR is in draft status
Using Azure CLI to deploy a 2019-Datacenter-GS image does not work, it returns an error of OS Provision Timed out. Maybe it does work if timeout is modified, but I am unable to verify that.
Please fix conflicting files
@yonzhan PR is ready
[Release] Update index.json for extension [ vm-repair ] : https://dev.azure.com/azclitools/release/_build/results?buildId=202634&view=results