Google Dataproc Job IAM
This page shows how to write Terraform for Dataproc Job IAM and write them securely.
The Job IAM in Dataproc can be configured in Terraform with the resource name
google_dataproc_job_iam. The following sections describe how to use the resource and its parameters.
Example Usage from GitHub
An example could not be found in GitHub.
The following arguments are supported:
job- (Required) The name or relative resource id of the job to manage IAM policies for.
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, email@example.com or firstname.lastname@example.org.
- serviceAccount:[emailid]: An email address that represents a service account. For example, email@example.com.
- group:[emailid]: An email address that represents a Google group. For example, firstname.lastname@example.org.
- 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_bindingcan be used per role. Note that custom roles must be of the format
policy_data- (Required) The policy data generated by a
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.
In addition to the arguments listed above, the following computed attributes are exported:
etag- (Computed) The etag of the jobs's IAM policy.
Explanation in Terraform Registry
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_dataproc_job_iam_policycannot be used in conjunction with
google_dataproc_job_iam_memberor they will fight over what your policy should be. In addition, be careful not to accidentally unset ownership of the job as
google_dataproc_job_iam_policyreplaces the entire policy.
google_dataproc_job_iam_bindingresources can be used in conjunction with
google_dataproc_job_iam_memberresources only if they do not grant privilege to the same role.