-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Question: No data source for KMS key/ring? #2847
Comments
It's true that we don't have them! If you do contribute them, please do so via https://github.com/GoogleCloudPlatform/magic-modules, where we have starting putting new code for Terraform in order to generate multiple versions of the provider and to autogenerate resources. |
Made a PR, it's a bit tricky to test but basic tests are there and the plugin #WORKSINMYCLOUD |
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! |
Google Cloud Platform does not support destruction of KMS keys/rings. There exists a data source for a
kms_secret
with a bit of a hack for getting it, but (as mentioned in #1214; and #518 mentions importing key/ring every single time: not a fun workflow) it looks like it would make more sense to have KMS keys and rings a data source (instead of having to reimport them each time).Is there a special reason why
data
source for KMS key/ring is not implemented? (I make a PR for one but wanted to ask first.)If you have a support request or question please submit them to one of these resources:
The text was updated successfully, but these errors were encountered: