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 google_kms_key_ring_iam_policy resource and improve iam docs #814

Merged
merged 2 commits into from
Dec 6, 2017

Conversation

rosbo
Copy link
Contributor

@rosbo rosbo commented Dec 1, 2017

  • Add a new resource google_kms_key_ring_iam_policy.
  • Improve IAM documentation for key ring.

The first time I looked at managing IAM policy with Terraform, I was very confused about when to use the policy vs member vs binding resource. I tried to improve our docs by grouping them together on one page and try my best to explain the differences between each.

Please review carefully the proposed documentation change. If y'all agree on it. I will update the IAM docs for the other resource types following the same format.

@rosbo rosbo requested a review from danawillow December 1, 2017 19:57
@rosbo rosbo requested review from paddycarver and danawillow and removed request for danawillow December 1, 2017 19:57
Copy link
Contributor

@paddycarver paddycarver left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's a great change and definitely clarifies the situation.

@rosbo rosbo merged commit d4e297e into hashicorp:master Dec 6, 2017
@rosbo rosbo deleted the iam_docs branch December 6, 2017 17:33
chrisst pushed a commit to chrisst/terraform-provider-google that referenced this pull request Nov 9, 2018
…hicorp#814)

* Add google_kms_key_ring_iam_policy resource and improve iam docs
* Delete iam_binding and iam_member specific doc page for key ring
modular-magician added a commit to modular-magician/terraform-provider-google that referenced this pull request Sep 27, 2019
@ghost
Copy link

ghost commented Mar 30, 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 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants