vm repair bitlocker key

[corsini-msft]

---

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

⚠️vm-repair

rule	cmd_name	rule_message	suggest_message
⚠️ 1006 - ParaAdd	vm repair create	cmd vm repair create added parameter encrypted_vm_recovery_password

[azure-client-tools-bot-prd]

Hi @corsini-msft,
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.

[yonzhan]

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

[github-actions]

⚠️ Release Suggestions

Module: vm-repair

• ⚠️ Please log updates into to src/vm-repair/HISTORY.rst
• Update VERSION to 1.1.0 in src/vm-repair/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

[canfikret]

perhaps "if encrypted_vm_recovery_password is not None:"

[corsini-msft]

Fixed in latest.

[dkulkarni-ms]

Could you explain me this logic bit? What if there is no bek file and there is no bit locker key. Else is removed.
Also when bitlocker key is set then this should be null $bekPartition.DriveLetter?

[corsini-msft]

I think this is largely fixed in latest push. Added elseif statements for when bitlockerkey is provided, and moved the logic to fetch the bek file into an early if block before the unlock-bitlocker cmd.