Adding stack-hci-vm 1.11.3#9436
Conversation
️✔️Azure CLI Extensions Breaking Change Test
|
|
Hi @yujiaucr, |
|
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>
|
|
There was a problem hiding this comment.
Pull Request Overview
This PR adds version 1.11.2 of the stack-hci-vm Azure CLI extension to the index.json file. According to the PR description, this follows the standard extension publishing workflow where only index.json is updated after the extension build.
- Adds new extension version entry with metadata and download URL
- Maintains consistency with previous version entries
- Follows the automated extension publishing process
| "license": "MIT", | ||
| "metadata_version": "2.0", | ||
| "name": "stack-hci-vm", | ||
| "summary": "Microsoft Azure Command-Line Tools Stack-HCi-VM Extension", |
There was a problem hiding this comment.
Inconsistent capitalization in 'HCi' - should be 'HCI' (all uppercase). While this matches the existing entries for this extension, the correct capitalization for 'HCI' (Hyper-Converged Infrastructure) is all uppercase.
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
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.