» IAM policy for Dataproc job

Three different resources help you manage IAM policies on dataproc jobs. Each of these resources serves a different use case:

• google_dataproc_job_iam_policy: Authoritative. Sets the IAM policy for the job and replaces any existing policy already attached.
• google_dataproc_job_iam_binding: Authoritative for a given role. Updates the IAM policy to grant a role to a list of members. Other roles within the IAM policy for the job are preserved.
• google_dataproc_job_iam_member: Non-authoritative. Updates the IAM policy to grant a role to a new member. Other members for the role for the job are preserved.

» google_pubsub_subscription_iam_policy

data "google_iam_policy" "admin" {
  binding {
    role    = "roles/editor"
    members = [
      "user:jane@example.com",
    ]
  }
}

resource "google_dataproc_job_iam_policy" "editor" {
  project      = "your-project"
  region       = "your-region"
  job_id       = "your-dataproc-job"
  policy_data  = "${data.google_iam_policy.admin.policy_data}"
}

» google_pubsub_subscription_iam_binding

resource "google_dataproc_job_iam_binding" "editor" {
  job_id       = "your-dataproc-job"
  role         = "roles/editor"
  members      = [
    "user:jane@example.com",
  ]
}

» google_pubsub_subscription_iam_member

resource "google_dataproc_job_iam_member" "editor" {
  job_id       = "your-dataproc-job"
  role         = "roles/editor"
  member       = "user:jane@example.com"
}

» Argument Reference

The following arguments are supported:

• job - (Required) The name or relative resource id of the job to manage IAM policies for.

For google_dataproc_job_iam_member or google_dataproc_job_iam_binding:

• member/members - (Required) Identities that will be granted the privilege in role. Each entry can have one of the following values:

  • allUsers: A special identifier that represents anyone who is on the internet; with or without a Google account.
  • allAuthenticatedUsers: A special identifier that represents anyone who is authenticated with a Google account or a service account.
  • user:{emailid}: An email address that represents a specific Google account. For example, alice@gmail.com or joe@example.com.
  • serviceAccount:{emailid}: An email address that represents a service account. For example, my-other-app@appspot.gserviceaccount.com.
  • group:{emailid}: An email address that represents a Google group. For example, admins@example.com.
  • domain:{domain}: A G Suite domain (primary, instead of alias) name that represents all the users of that domain. For example, google.com or example.com.

• role - (Required) The role that should be applied. Only one google_dataproc_job_iam_binding can be used per role. Note that custom roles must be of the format [projects|organizations]/{parent-name}/roles/{role-name}.

google_dataproc_job_iam_policy only: * policy_data - (Required) The policy data generated by a google_iam_policy data source.

• project - (Optional) The project in which the job belongs. If it is not provided, Terraform will use the provider default.

• region - (Optional) The region in which the job belongs. If it is not provided, Terraform will use the provider default.

» Attributes Reference

In addition to the arguments listed above, the following computed attributes are exported:

• etag - (Computed) The etag of the jobs's IAM policy.

» Import

Job IAM resources can be imported using the project, region, job id, role and/or member.

$ terraform import google_dataproc_job_iam_policy.editor "projects/{project}/regions/{region}/jobs/{job_id}"

$ terraform import google_dataproc_job_iam_binding.editor "projects/{project}/regions/{region}/jobs/{job_id} roles/editor"

$ terraform import google_dataproc_job_iam_member.editor "projects/{project}/regions/{region}/jobs/{job_id} roles/editor user:jane@example.com"