-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows OS disk encryption (disk encryption set) cannot be updated after VM is created #6737
Comments
Hi @kumarkran thanks for this issue! |
…n settings (hashicorp#6846) Fixes hashicorp#6737 This applies the changes in PR hashicorp#6230 to windows virtual machine which only fixes the problem in linux virtual machine despite its title says linux|windows.
This has been released in version 2.10.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example: provider "azurerm" {
version = "~> 2.10.0"
}
# ... other configuration ... |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
Community Note
Terraform (and AzureRM Provider) Version
`Terraform v0.12.18
`
Affected Resource(s)
azurerm_windows_virtual_machine
Terraform Configuration Files
Expected Behavior
Windows OS disk encryption set updated to existing VM's
Actual Behavior
Unable to update OS disk encryption (Disk encryption set) for existing VM's
Steps to Reproduce
Terraform apply
VM initially without disk encryption set3.Run terraform apply after updating disk encryption set id
Important Factoids
This issue is similar to #6183
Only Linux VM' got the fix in #6230
The text was updated successfully, but these errors were encountered: