{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

• [x] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• [x] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
• [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-client-tools-bot-prd[bot]]

️✔️Azure CLI Extensions Breaking Change Test

>

>

️✔️Non Breaking Changes

> > >

[azure-client-tools-bot-prd[bot]]

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[bot]]

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[bot]]

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[bot]]

Azure Pipelines successfully started running 2 pipeline(s).

[yanzhudd]

Hi @Sandido please resolve the code conflicts

[Sandido]

@yanzhudd please re-review