{vm-repair} Overhaul VM Repair examples

[Sandido]

---

This checklist is used to make sure that common guidelines for a pull request are followed.

Related command

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
• My extension version conforms to the Extension version schema

For new extensions:

• 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-client-tools-bot-prd]

️✔️Azure CLI Extensions Breaking Change Test

️✔️Non Breaking Changes

[azure-client-tools-bot-prd]

Hi @Sandido,
Since the current milestone time is less than 7 days, this pr may not catch up with this release.

[azure-client-tools-bot-prd]

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.

[github-actions]

Hi @Sandido

Release Suggestions

Module: vm-repair

• Update VERSION to 2.0.2 in src/vm-repair/setup.py

Notes

• For more info about extension versioning, please refer to Extension version schema

[yonzhan]

VM Repair

[Sandido]

@zhoxing-ms , @yanzhudd , please review.

[yanzhudd]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[yanzhudd]

Hi @Sandido
please resolve the code conflicts

[Sandido]

@yanzhudd please re-review

[Sandido]

@yanzhudd , I committed your suggestions. I am not familiar with using Upcoming as a version though. If that is the new best practice, then that's good by me. Else 2.0.2 is fine.

[yanzhudd]

@yanzhudd , I committed your suggestions. I am not familiar with using Upcoming as a version though. If that is the new best practice, then that's good by me. Else 2.0.2 is fine.

If you put features into upcoming, the features are currently in a pending release status. You can move them to a new version later like 2.0.2 when you want to release them.

[yanzhudd]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[Sandido]

@yanzhudd , do I need to do anything to manually release a new version of the cli extension or does the cli team do that automatically?

[yanzhudd]

@yanzhudd , do I need to do anything to manually release a new version of the cli extension or does the cli team do that automatically?

You can determine when to release a new version and what version will be. The extension module is flexible and can be controlled by yourself.
You need to modify the HISTORY.rst and setup.py files if you want to release a new version for it (You can refer to this PR: https://github.com/Azure/azure-cli-extensions/pull/8000/files). After the modification, the new version will be released automatically in about a tens of minutes.

However, please note that all releases are currently frozen due to CCOA, so please do not release any version for now.

[yanzhudd]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[github-actions]

🚫All pull requests will be blocked to merge until Jan 6, 2025 due to CCOA