Default for undefined booleans without default (azurerm_storage_account/enable_blob_encryption)

[anoff]

Terraform Version

Terraform v0.11.5

• provider.azurerm v1.3.0

Affected Resource(s)

• azurerm_storage_account

Terraform Configuration Files

resource "azurerm_storage_account" "backend" {
  name                     = "mybackend"
  resource_group_name      = "${azurerm_resource_group.backend.name}"
  location                 = "${azurerm_resource_group.backend.name.location}"
  account_tier             = "Standard"
  account_kind             = "StorageV2"
  account_replication_type = "GRS"
}

I was wondering how TF handles boolean values that are set to computed if there is no default present.
The one I am especially interested in is enable_blob_encryption option. I assume since the code does not specify a default: true it will go to 0 -> false.

However since Azure enforces encryption on all storage accounts per default I wonder how Terraform behaves in this scenario.

[MMollyy]

+1
I am noticing the behaviour where terraform defaults to False - while the azure platform defaults to true.
Multiple storage accounts.

[katbyte]

Hello @anoff,

While the code does not specify a default of true, it only passing a value of true or false to the API if the property is set that then defaults to true. However i understand the confusion so have opened #1380 to explicitly set the default to true.

@MarcoMol, could you provide some example terraform where the provider ends up defaulting to false? thank you

[MMollyy]

Hi @katbyte,

of course, here goes:

resource "azurerm_storage_account" "id" {
  account_tier             = "Standard"
  resource_group_name      = "${azurerm_resource_group.name.name}"
  name                     = "name"
  account_replication_type = "GRS"
  location                 = "westeurope"
  account_kind             = "StorageV2"
}

the other storage account is the same, but LRS.

[katbyte]

Hi @MarcoMol,

Thank you for providing the config, updated #1380 as a result and this should be fixed in 1.7.0.

[katbyte]

Hey @anoff @MarcoMol,

We just released 1.7 today that included the fix for this issue, hope it solves it for you two!

[anoff]

@katbyte thanks a lot for keeping us updated

[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 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 👉 hashibot-feedback@hashicorp.com. Thanks!