azurerm_storage_blobs can't be attached to vms since v.0.9.3

[juls]

Hi there,

since this commit, a existing azurerm_storage_blob can't be attached to a azurerm_virtual_machine anymore. It fails because this test only allows attaching a managed disk.

Terraform Version

Terraform v0.9.3

Affected Resource(s)

• azurerm_virtual_machine
• azurerm_storage_blob

Terraform Configuration Files

Based on the azurerm_virtual_machine example:

resource "azurerm_storage_blob" "test" {
  name                    = "datadisk0.vhd"
  resource_group_name     = "${azurerm_resource_group.test.name}"
  storage_account_name    = "${azurerm_storage_account.test.name}"
  storage_container_name  = "${azurerm_storage_container.test.name}"
  source_uri              = "https://accsa.blob.core.cloudapi.de/images/empty-1024gb.vhd"
  type                    = "page"
  size                    = "1099511627776"
}

resource "azurerm_virtual_machine" "test" {
[...]
  storage_data_disk {
    name          = "datadisk0"
    vhd_uri       = "${azurerm_storage_account.test.primary_blob_endpoint}${azurerm_storage_container.test.name}/datadisk0.vhd"
    disk_size_gb  = "1023"
    create_option = "Attach"
    lun           = 0
  }
[...]

Expected Behavior

An existing image should be attached. This worked fine until Terraform v0.9.2.

Actual Behavior

Since this was added, it fails with
* azurerm_virtual_machine.test: [ERROR] Must specify which disk to attach

Steps to Reproduce

1. Take the example from the documentation
2. Add the above mentioned azurerm_storage_blob. source_uri can be any existing image.
3. Change the create_option to Attach, as shown above to attach that existing image.
4. run terraform apply
5. After a while, see the above mentioned error message.

[brandontosch]

Ick, my bad. I'll get a PR open for the fix as soon as I can.

[brandontosch]

Opened PR #13686 for the fix.

[ghost]

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.