-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
LastAccessTimeBasedTracking is not supported for the account #11853
Comments
We face the same problem. We are working with Modules:
We are deploying to west europe. kr tom |
Same configuration, same version, same bug. |
Fixed with version |
This has been released in version 2.63.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example: provider "azurerm" {
version = "~> 2.63.0"
}
# ... other configuration ... |
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. |
Community Note
Terraform (and AzureRM Provider) Version
Affected Resource(s)
azurerm_storage_account
Terraform Configuration Files
Expected Behaviour
Actual Behaviour
Steps to Reproduce
terraform apply
Important Factoids
We used that setup for about 3 weeks but since Monday (May 24, 2021), the error above occurs. To reproduce the problem you need to setup
is_hns_enabled = true
together with theblob_properties
block.The problem occurs only with provider version
>=2.57.0
and seems related to the PR #11301.References
azurerm_storage_account
support forchange_feed
, versioning_enabled,
default_service_version, and
last_access_time_enabledwithin the
blob_properties` block #11301The text was updated successfully, but these errors were encountered: