Terraform 0.12.6
AzureRM Provider 1.32.1
Storage Accounts
azurerm_storage_accountresource "azurerm_storage_account" "storage_account_terraform" {
name = "storagename"
location = azurerm_resource_group.resource_group_terraform.location
resource_group_name = azurerm_resource_group.resource_group_terraform.name
account_kind = "Storage"
account_tier = "Standard"
account_replication_type = "LRS"
enable_https_traffic_only = true
network_rules {
ip_rules = var.public_ip_region_list
}
tags = {
Department = "test"
projectName = "test"
}
}
Running terraform plan should not fail.
Running terraform plan fails with:
Error: Error reading queue properties for AzureRM Storage Account "storageaccount": queues.Client#SetServiceProperties: Failure responding to request: StatusCode=403 -- Original Error: autorest/azure: error response cannot be parsed: "\ufeffAuthenticationFailed
terraform planRunning in US Government Cloud
Git 3997 is very similar, but not an identical error. As with 3997, I can downgrade to 1.31.0 to avoid the issue. If I update to 1.32.0, I get an error about advanced threat protection (due to it not being available in Gov), which is resolved with 1.32.1, but 1.32.1 triggers this issue.
As @tombuildsstuff pointed out, 3939 is a better match. Thanks!
hi @sladeedmonds
Thanks for opening this issue :)
Taking a look through this appears to be a duplicate of #3939 - rather than having multiple issues open tracking the same thing I'm going to close this issue in favour of that one; would you mind subscribing to #3939 for updates?
Thanks!
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!
Most helpful comment
hi @sladeedmonds
Thanks for opening this issue :)
Taking a look through this appears to be a duplicate of #3939 - rather than having multiple issues open tracking the same thing I'm going to close this issue in favour of that one; would you mind subscribing to #3939 for updates?
Thanks!