fix(e2e): fix argument for az sig image-version create #968
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It appears there's been a regression in version 2.59.0 of the Azure CLI, where az sig image-version create fails when being passed the --managed-image flag, see the related failing CI run, and the reported issue on the azure-cli project.
Because of this we are not able to create new versions for any of our VM templates.
To fix this we can apply the workaround from the linked issue and pass the VM ID inside the
--virtual-machine
argument. I've tested this locally and successfully created a new image version with the change.Partly fixes UDENG-2528