[AVM Module Issue]: PremiumSSDv2 change breaks existing deployments

[dennyhabich]

Check for previous/existing GitHub issues

• I have checked for previous/existing GitHub issues

Issue Type?

Bug

Module Name

avm/res/compute/virtual-machine

(Optional) Module Version

No response

Description

The changes to support PremiumSSDv2 disks, doesn't seem to be backwards compatible with VMs that were deployed before this change. The error I'm getting is

Changing property 'dataDisk.createOption' is not allowed.

The data disks where created with createOption 'Empty'. Looking at the module changes, the createOption is probably changing into 'Attached', which is not allowed.
Is there a solution or workaround for this?

(Optional) Correlation Id

No response

[microsoft-github-policy-service]

Important

The "Needs: Triage 🔍" label must be removed once the triage process is complete!

Tip

For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation.

[avm-team-linter]

@dennyhabich, thanks for submitting this issue for the avm/res/compute/virtual-machine module!

Important

A member of the @Azure/avm-res-compute-virtualmachine-module-owners-bicep or @Azure/avm-res-compute-virtualmachine-module-contributors-bicep team will review it soon!

[microsoft-github-policy-service]

Warning

Tagging the AVM Core Team (@Azure/avm-core-team-technical-bicep) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.

Tip

• To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
• To avoid this rule being (re)triggered, the ""Needs: Triage 🔍" label must be removed as part of the triage process (when the issue is first responded to)!

[rahalan]

@dennyhabich thanks for bringing this up. Will investigate. For now you would need to use the old version of the module for the older VMs