[Sayan Naskar (nascarsayan)]

Changes to connectedvmware extension:

• Refresh sdk from latest public facing swagger
• Raise better error types instead of CLIError
• revamping get_resource_id utility function to take into account multiple children. Thoroughly verified its behaviour using unittests
• If only tags are intended to be updated for vm, just update Machine tags, and dont call update for VMInstance.
• machine.kind case insensitive check.

---

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?

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 Sayan Naskar (@nascarsayan),
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.

[Yong Zhang (yonzhan)]

connectedvmware

[Azure CLI Bot (azclibot)]

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