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. 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
IAM keys can be managed by non-authoritative member resource, or authoritative-for-a-role binding resource, however the policy resource seems to be missing for KMS Crypto Keys. This just seems like an oversight in #781 (or perhaps IAM didn't support it at the time?).
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
Feb 2, 2020
Community Note
Description
IAM keys can be managed by non-authoritative
member
resource, or authoritative-for-a-rolebinding
resource, however thepolicy
resource seems to be missing for KMS Crypto Keys. This just seems like an oversight in #781 (or perhaps IAM didn't support it at the time?).New or Affected Resource(s)
google_kms_crypto_key_iam_policy
Potential Terraform Configuration
References
https://github.com/terraform-providers/terraform-provider-google/pulls/781
#762
The text was updated successfully, but these errors were encountered: