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 an issue is assigned to a user, that user is claiming responsibility for the issue.
Customers working with a Google Technical Account Manager or Customer Engineer can ask them to reach out internally to expedite investigation and resolution of this issue.
Community Note
Description
Please update the document about google_project_iam_binding resource (https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/google_project_iam).
Today my project uses google_project_iam_binding and it removes roles that other principals like Service Account already have this role from before, which leads to an accident in the production environment. I see a discussion about this issue here https://discuss.hashicorp.com/t/difference-between-google-project-iam-binding-and-google-project-iam-member/49645/2.
Lack of description about this resource may lead to miss understanding for new users about it
New or Affected Resource(s)
google_project_iam_binding
Potential Terraform Configuration
References
No response
The text was updated successfully, but these errors were encountered: