-
Notifications
You must be signed in to change notification settings - Fork 9.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
Add support for Customer supplied Encryption in Google #5053
Comments
disclaimer: i use the google provider a lot but i neither work for google nor am i a terraform committer. It's still a beta feature. To access it, Terraform would have to use the beta gcloud go SDK. gcloud resources refer to each by what i'm saying is even if it's a trivial change to map a single resource attribute to a single field in a map passed to the SDK, use of the beta SDK itself has widespread ramifications. |
Hi here, CSEK(customer supplied encryption key) is now generally available since the 2016/08/01 |
Looks like this issue addressed in #11167 |
Yes, this is done. |
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Google has added since a few months the ability to use Customer supplied encryption in GCE. It would be good if Terraform offered an encryption parameter in google_compute_instance and google_compute_disk resources
The text was updated successfully, but these errors were encountered: