The multi config scenario is failing at delete operation:
azure.core.exceptions.ResourceExistsError: (OperationNotAllowed) Operation 'Delete VM Extension' is not allowed on VM Extension 'MCExt1' as it is installed and managed by Compute Resource Provider. Code: OperationNotAllowed Message: Operation 'Delete VM Extension' is not allowed on VM Extension 'MCExt1' as it is installed and managed by Compute Resource Provider.
RunCommandHandler is an implicit extension, which cannot be managed by regular extension api.
After talking with Vivek, the virtual machine run command api is the correct api to use for runcommand operations. This PR adds a runcommand client for these operations.
Issue #
PR information
[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which has an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] If applicable, the PR references the bug/issue that it fixes in the description.
[ ] New Unit tests were added for the changes made
Description
The multi config scenario is failing at delete operation:
azure.core.exceptions.ResourceExistsError: (OperationNotAllowed) Operation 'Delete VM Extension' is not allowed on VM Extension 'MCExt1' as it is installed and managed by Compute Resource Provider. Code: OperationNotAllowed Message: Operation 'Delete VM Extension' is not allowed on VM Extension 'MCExt1' as it is installed and managed by Compute Resource Provider.RunCommandHandler is an implicit extension, which cannot be managed by regular extension api. After talking with Vivek, the virtual machine run command api is the correct api to use for runcommand operations. This PR adds a runcommand client for these operations.
Issue #
PR information
Quality of Code and Contribution Guidelines