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

Add protection_level for resource google_kms_crypto_key #2723

Closed
kawsark opened this issue Dec 20, 2018 · 4 comments
Closed

Add protection_level for resource google_kms_crypto_key #2723

kawsark opened this issue Dec 20, 2018 · 4 comments
Assignees

Comments

@kawsark
Copy link

kawsark commented Dec 20, 2018

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. If the issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.

Description

New or Affected Resource(s)

Potential Terraform Configuration

The GCP Terraform Provider should provide a protection_level option for creating keys with a specific protection_level. E.g:

resource "google_kms_crypto_key" "my_crypto_key" {
  name            = "my-crypto-key"
  key_ring        = "${google_kms_key_ring.my_key_ring.self_link}"
  rotation_period = "100000s"
  protection_level = “hsm”
}

References

@ghost ghost added the enhancement label Dec 20, 2018
@Bastiat99
Copy link

This would be a great help for deploying secure architectures. Tracking for progress.

@rileykarson
Copy link
Collaborator

This should be released in version 2.0.0 of the provider.

@Bastiat99
Copy link

Thanks, Riley.

@ghost
Copy link

ghost commented Jan 27, 2019

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 Jan 27, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants