-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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 resources google_cloud_tasks_queue_iam_* #6599
Add resources google_cloud_tasks_queue_iam_* #6599
Comments
For those looking for a temporary solution, you can run gcloud commands directly from Terraform which can set up fine grained permissions on queues. module "queue_permission" {
source = "terraform-google-modules/gcloud/google"
version = "~> 2.0"
create_cmd_body = "tasks queues add-iam-policy-binding ${google_cloud_tasks_queue.<queue_name>.id} --member=serviceAccount:${google_service_account.<service_account_name>.email} --role=roles/cloudtasks.enqueuer"
destroy_cmd_body = "tasks queues remove-iam-policy-binding ${google_cloud_tasks_queue.<queue_name>.id} --member=serviceAccount:${google_service_account.<service_account_name>.email} --role=roles/cloudtasks.enqueuer"
} |
Any updates on this? |
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. |
Community Note
Description
It would be great to have the queue-level IAM policy resources to avoid having to grant project-level roles/tasks.enqueuer to service accounts that only need access to a single queue. Thanks!
New or Affected Resource(s)
Potential Terraform Configuration
The text was updated successfully, but these errors were encountered: