You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
enable_blob_encryption and enable_file_encryption arguments are not needed anymore for azurerm_storage_account resources, as Azure Storage encryption is enabled for all new and existing storage accounts and cannot be disabled. (as stated in https://docs.microsoft.com/en-us/azure/storage/common/storage-service-encryption)
Setting either enable_blob_encryption or enable_file_encryption to false results in it being set to true nevertheless.
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!
ghost
locked and limited conversation to collaborators
Mar 28, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Description
enable_blob_encryption
andenable_file_encryption
arguments are not needed anymore forazurerm_storage_account
resources, as Azure Storage encryption is enabled for all new and existing storage accounts and cannot be disabled. (as stated in https://docs.microsoft.com/en-us/azure/storage/common/storage-service-encryption)Setting either
enable_blob_encryption
orenable_file_encryption
tofalse
results in it being set totrue
nevertheless.New or Affected Resource(s)
References
The text was updated successfully, but these errors were encountered: