Skip to content
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

Remove storage account encryption arguments because encryption cannot be disabled #3820

Closed
irnc opened this issue Jul 10, 2019 · 2 comments · Fixed by #5668
Closed

Remove storage account encryption arguments because encryption cannot be disabled #3820

irnc opened this issue Jul 10, 2019 · 2 comments · Fixed by #5668

Comments

@irnc
Copy link

irnc commented Jul 10, 2019

Community Note

  • 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.

New or Affected Resource(s)

  • azurerm_storage_account

References

@ghost
Copy link

ghost commented Feb 24, 2020

This has been released in version 2.0.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.0.0"
}
# ... other configuration ...

@ghost
Copy link

ghost commented Mar 28, 2020

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 ghost locked and limited conversation to collaborators Mar 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.