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

Feature request: support for Google IAM policies on PubSub topics #13602

Closed
pdecat opened this issue Apr 12, 2017 · 2 comments
Closed

Feature request: support for Google IAM policies on PubSub topics #13602

pdecat opened this issue Apr 12, 2017 · 2 comments

Comments

@pdecat
Copy link
Contributor

pdecat commented Apr 12, 2017

Hi, I would love to see the addition of a google_pubsub_topic_iam_policy resource to manage IAM policies on PubSub topics:

Following is an example of what this would look like setting an IAM policy on a pubsub topic:

resource "google_service_account" "publisher" {
  account_id   = "publisher"
  display_name = "Publisher"
}

resource "google_pubsub_topic" "default" {
  name = "default-topic"
}

data "google_iam_policy" "topic_publisher" {
  binding {
    role = "roles/pubsub.publisher"

    members = [
      "serviceAccount:${google_service_account.publisher.email}",
    ]
  }
}

# THE FOLLOWING RESOURCE DOES NOT EXIST YET!
resource "google_pubsub_topic_iam_policy" "default_topic_publisher" {
  target      = "${google_pubsub_topic.default.name}"
  policy_data = "${data.google_iam_policy.topic_publisher.policy_data}"
}

PS: If this feature request is accepted, should I open other issues for the other resources I am willing to see support? Or should this issue be renamed and updated to track everything in one place?

@evmin
Copy link

evmin commented Jun 6, 2017

+1
I would also be interested in explicit subscription permissions.

Pubsub and Bigquery are probably the most needed resources.

@ghost
Copy link

ghost commented Apr 9, 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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 9, 2020
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

5 participants