-
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
2.19.0 set azurerm_storage_account with allow_blob_public_access = true by default #7820
Comments
The current behaviour in 2.19 is actually the expected behaviour. If you run In the link above which explains anonymous read access Azure treats null and true to be the same on the property
In updating the provider to 2.19 it appears Terraform treats null as false which is why the provider is updating the property to true as its default. So what will happen is the allowBlobPublicAccess property will be set to true which previously null was being treated the same. |
@pierreyvesv The default behavior was fixed at #7784 . Could please will for the new feature release. Thanks for opening the issue! |
you are right ! 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 👉 hashibot-feedback@hashicorp.com. Thanks! |
Community Note
Terraform (and AzureRM Provider) Version
$ terraform -v
Terraform v0.12.28
Affected Resource(s)
azurerm_storage_account
Debug Output
Since 2.19.0 allow_blob_public_access is set to "true" by default and update to resource show the following plan:
Expected Behavior
allow_blob_public_access should be set to false by default.
if I understand it well public access has to be explicitly enable
Actual Behavior
since 2.19.0 allow_blob_public_access is set to true by default
Steps to Reproduce
terraform plan
with the following resourceThe text was updated successfully, but these errors were encountered: