Bugfix

[qwuae1]

---

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 @qwuae1,
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.

[azure-client-tools-bot-prd]

Hi @qwuae1,
Since the current milestone time is less than 7 days, this pr will be reviewed in the next milestone.

[yonzhan]

Thank you for your contribution! We will review the pull request and get back to you soon.

[qwuae1]

/azp run

[azure-pipelines]

Commenter does not have sufficient privileges for PR 7436 in repo Azure/azure-cli-extensions

[qwuae1]

@zhoxing-ms
may you help me with approval and merge

[yonzhan]

Please fix CI issues

[zhoxing-ms]

Could you explain in detail what this description means?

[qwuae1]

@zhoxing-ms
yeah, the null string check is not working as the string is return empty
now setting the branch to the correct repo

updated the his rst

[zhoxing-ms]

I would like to confirm with you whether there is a security risk in exposing these keys to the public in the open source code?

[qwuae1]

make this change separated
linter passed locally

[zhoxing-ms]

Please fix the azdev linter issue: https://dev.azure.com/azclitools/public/_build/results?buildId=144943&view=logs&j=e2e497a5-ba27-5eb9-f39e-d929d56974a6&t=61cc2d02-f6f4-5007-71e9-5651933c3fe7

[qwuae1]

Please fix the azdev linter issue: https://dev.azure.com/azclitools/public/_build/results?buildId=144943&view=logs&j=e2e497a5-ba27-5eb9-f39e-d929d56974a6&t=61cc2d02-f6f4-5007-71e9-5651933c3fe7
@zhoxing-ms
linter passed locally now

[github-actions]

⚠️ Suggestions

Module: vm-repair

• Update version to 1.0.2 in setup.py

Notes

• Stable/preview tag is inherited from last release. If needed, please add stable/preview label to modify it.
• Major/minor/patch/pre increment of version number is calculated by pull request code changes automatically. If needed, please add major/minor/patch/pre label to adjust it.
• For more info about extension versioning, please refer to Extension version schema

[zhoxing-ms]

Please take a look at this comment: #7436 (comment)

If you want to release a new extension version, please update the version in setup.py as well

[qwuae1]

Please take a look at this comment: #7436 (comment)

If you want to release a new extension version, please update the version in setup.py as well

thx, resolve it

[azclibot]

[Release] Update index.json for extension [ vm-repair ] : https://dev.azure.com/azclitools/internal/_build/results?buildId=145001&view=results