You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to use an azure_virtual_machine_extension to encrypt disks of a VM also created by terraform. My vm has an os disk and data disk. The data disk is a managed disk created by terraform.
I am not sure if there is something wrong with my config or if this is a known issue. At the very least, it would be nice to have an example of how to do this.
The azure_virtual_machine_extension should enable disk encryption on the VM it is attached to.
Actual Behavior
The azure_virtual_machine_extension is created successfully, but disk encryption isn't enabled on the VM's disks.
Important Factoids
The azure_virtual_machine_extension is created successfully. Running the following Azure CLI command enables the extension on the VM it is associated with:
az vm encryption enable --aad-client-id "<my_client_id>" --disk-encryption-keyvault linuxvmexample --name example-linux-vm --resource-group linux-vm-resource-group-example-resource-group --aad-client-secret "<my_client_secret>" --volume-type ALL
This command is not creating a new extension as running a terraform destroy still correctly removes the extension created by terraform and no new extensions appear with the VM in the Azure Portal.
The only difference I can find after running az vm extension list before and after running the az vm encryption command is the addition of a SequenceVersion key-value pair.
The text was updated successfully, but these errors were encountered:
At this time the Azure Provider doesn't support Disk Encryption on Virtual Machines using the azurerm_virtual_machine resource - however it's something we're looking to support in the near future. There's a feature request open for this in #486, which I'm going to close this in favour of.
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!
ghost
locked and limited conversation to collaborators
Mar 31, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am trying to use an
azure_virtual_machine_extension
to encrypt disks of a VM also created by terraform. My vm has an os disk and data disk. The data disk is a managed disk created by terraform.I am not sure if there is something wrong with my config or if this is a known issue. At the very least, it would be nice to have an example of how to do this.
Terraform Version
Affected Resource(s)
azure_virtual_machine
azure_virtual_machine_extension
Terraform Configuration Files
Expected Behavior
The
azure_virtual_machine_extension
should enable disk encryption on the VM it is attached to.Actual Behavior
The
azure_virtual_machine_extension
is created successfully, but disk encryption isn't enabled on the VM's disks.Important Factoids
The
azure_virtual_machine_extension
is created successfully. Running the following Azure CLI command enables the extension on the VM it is associated with:This command is not creating a new extension as running a
terraform destroy
still correctly removes the extension created by terraform and no new extensions appear with the VM in the Azure Portal.The only difference I can find after running
az vm extension list
before and after running theaz vm encryption
command is the addition of aSequenceVersion
key-value pair.The text was updated successfully, but these errors were encountered: