Open chrisnavar opened 1 month ago
If I do the same deployment of the above configuration file with the hotpatching_enabled parameter set on 'false' it works as per normal behaviour, but then if I modify again this hotpatching_enabled parameter to 'true', terraform completes successfully the changes on the already deployed VM.
Is there an existing issue for this?
Community Note
Terraform Version
1.8.4
AzureRM Provider Version
3.101.0
Affected Resource(s)/Data Source(s)
azurerm_windows_virtual_machine
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
Terraform should create the virtual machine when hotpatching_enabled = true as the SKU supports the functionality.
Actual Behaviour
Terraform prevents the virtual machine from being created and outputs the above error.
Steps to Reproduce
No response
Important Factoids
No response
References
No response