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

bigtable instance level IAM binding or role members #3750

Closed
Charles546 opened this issue May 30, 2019 · 2 comments
Closed

bigtable instance level IAM binding or role members #3750

Charles546 opened this issue May 30, 2019 · 2 comments

Comments

@Charles546
Copy link

Charles546 commented May 30, 2019

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

I couldn't find a resource in the google provider for terraform to add IAM bindings for bigtable on the instance level.

I am able to add role members on instance level through gcloud console UI. I am assuming it should be possible to do it through API.

New or Affected Resource(s)

  • google_bigtable_instance_iam_member
  • google_bigtable_instance_iam_binding

Potential Terraform Configuration

resource "google_bigtable_instance_iam_member" "test" {
  bigtable_instance_name = "test"
  role                 = "roles/bigtable.user"
  members            = [
    "serviceAccount:xxxx",
    "group:xxxx",
  ]
}

References

@danawillow
Copy link
Contributor

Closing as duplicate of #3488.

@ghost
Copy link

ghost commented Jul 29, 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 Jul 29, 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

2 participants