-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
LastAccessTimeBasedTiering is not supported for the account #23133
Comments
I'm seeing the same issue - it seems like having This seems to have started happening in v3.63.0. v3.62 works fine. I'm wondering if this bugfix caused a regression?
terraform {
required_version = ">= 1.3.3"
backend "local" {}
# See #2 above before changing
required_providers {
azurerm = {
source = "hashicorp/azurerm"
version = "=3.71.0"
}
}
}
provider "azurerm" {
features {
key_vault {
purge_soft_delete_on_destroy = false
}
}
}
resource "azurerm_resource_group" "primary" {
name = "justintest2"
location = "eastus"
}
resource azurerm_storage_account "account" {
account_kind = "Storage"
account_replication_type = "LRS"
account_tier = "Standard"
allow_nested_items_to_be_public = false
cross_tenant_replication_enabled = false
default_to_oauth_authentication = false
enable_https_traffic_only = true
infrastructure_encryption_enabled = false
is_hns_enabled = false
location = "eastus2"
min_tls_version = "TLS1_2"
name = "stjustinbroken"
nfsv3_enabled = false
public_network_access_enabled = true
queue_encryption_key_type = "Service"
resource_group_name = azurerm_resource_group.primary.name
sftp_enabled = false
shared_access_key_enabled = true
table_encryption_key_type = "Service"
# omitting blob_properties will cause this to succeed.
blob_properties {
change_feed_enabled = false
last_access_time_enabled = false
versioning_enabled = false
}
} |
Is this happeninig in usgov cloud, or public cloud? |
Public cloud |
we're working around it by having our terraform exclude blob properties entirely if the storage account is a v1 account. This works for us since we don't set any blob properties on them - but some of those properties are supported in v1 accounts and its not clear how you would use them if these others are automatically set if you include the blob props stanza. |
@melvis02 Could you please provide a minimal valid TF config with values filled so that I can use it to reproduce locally? @justinrush Yes, it looks like a regression. Whilst as @melvis02 mentioned, the issue also exist in public cloud. Presumably, these are due to different causes? |
My reply can serve as a minimal tf config |
@justinrush Then it sounds both the |
Ran into this issue when creating a new storage account today with 3.72.0 Hoping this will be resolved soon. I'm trying to move to 3.62.0 to see if that at least gets me un-stuck |
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. |
Is there an existing issue for this?
Community Note
Terraform Version
1.3.3
AzureRM Provider Version
3.71.0
Affected Resource(s)/Data Source(s)
azurerm_storage_account
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
Apply complete! Resources: x added, 0 changed, 0 destroyed.
Actual Behaviour
Steps to Reproduce
terraform apply
Important Factoids
I'm moving from azurerm 3.46 to latest (3.71) to get past 3.63 to take on some new features. I haven't regression tested each version, but jumping back to 3.69.0 and to 3.63.0 resulted in the same issue.
References
#11853 appears to be the same issue, addressed two years ago, in 2.63.
The text was updated successfully, but these errors were encountered: