Azure / Azure/bicep-registry-modules

[AVM Module Issue]: PremiumSSDv2 change breaks existing deployments

Open
#3,874 5 comments 0 reactions 1 assignee Assigned to @josunefon View on GitHub
Class: Resource Module :package: Type: AVM :a: :v: :m: Type: Bug :bug:
Dominant language
Bicep
Stars
736
Forks
564
Avg merge
3d 15h
Merged PRs (30d)
30

Description

### Check for previous/existing GitHub issues

- [x] 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_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.