Three different resources help you manage IAM policies on dataproc clusters. Each of these resources serves a different use case:
google_dataproc_cluster_iam_policy
: Authoritative. Sets the IAM policy for the cluster and replaces any existing policy already attached.google_dataproc_cluster_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 cluster are preserved.google_dataproc_cluster_iam_member
: Non-authoritative. Updates the IAM policy to grant a role to a new member. Other members for the role for the cluster are preserved.data "google_iam_policy" "admin" {
binding {
role = "roles/editor"
members = [
"user:jane@example.com",
]
}
}
resource "google_dataproc_cluster_iam_policy" "editor" {
project = "your-project"
region = "your-region"
cluster = "your-dataproc-cluster"
policy_data = data.google_iam_policy.admin.policy_data
}
resource "google_dataproc_cluster_iam_binding" "editor" {
cluster = "your-dataproc-cluster"
role = "roles/editor"
members = [
"user:jane@example.com",
]
}
resource "google_dataproc_cluster_iam_member" "editor" {
cluster = "your-dataproc-cluster"
role = "roles/editor"
member = "user:jane@example.com"
}
The following arguments are supported:
cluster
- (Required) The name or relative resource id of the cluster to manage IAM policies for.For google_dataproc_cluster_iam_member
or google_dataproc_cluster_iam_binding
:
member/members
- (Required) Identities that will be granted the privilege in role
.
Each entry can have one of the following values:
role
- (Required) The role that should be applied. Only one
google_dataproc_cluster_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_cluster_iam_policy
only:
policy_data
- (Required) The policy data generated by a google_iam_policy
data source.project
- (Optional) The project in which the cluster belongs. If it
is not provided, Terraform will use the provider default.
region
- (Optional) The region in which the cluster 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 clusters's IAM policy.IAM member imports use space-delimited identifiers that contain the resource's cluster
, role
, and member
. For example:
"projects/{project}/regions/{region}/clusters/{cluster} roles/editor user:jane@example.com"
An import
block (Terraform v1.5.0 and later) can be used to import IAM members:
import {
id = "projects/{project}/regions/{region}/clusters/{cluster} roles/editor user:jane@example.com"
to = google_dataproc_cluster_iam_member.default
}
The terraform import
command can also be used:
$ terraform import google_dataproc_cluster_iam_member.default "projects/{{project_id}}/datasets/{{dataset_id}} roles/viewer user:foo@example.com"
IAM binding imports use space-delimited identifiers that contain the resource's cluster
, role
. For example:
"projects/{project}/regions/{region}/clusters/{cluster} roles/editor"
An import
block (Terraform v1.5.0 and later) can be used to import IAM bindings:
import {
id = "projects/{project}/regions/{region}/clusters/{cluster} roles/editor"
to = google_dataproc_cluster_iam_binding.default
}
The terraform import
command can also be used:
$ terraform import google_dataproc_cluster_iam_binding.default "projects/{project}/regions/{region}/clusters/{cluster} roles/editor"
IAM policy imports use the cluster
identifier of the Dataproc Cluster resource only. For example:
projects/{project}/regions/{region}/clusters/{cluster}
An import
block (Terraform v1.5.0 and later) can be used to import IAM policies:
import {
id = projects/{project}/regions/{region}/clusters/{cluster}
to = google_dataproc_cluster_iam_policy.default
}
The terraform import
command can also be used:
$ terraform import google_dataproc_cluster_iam_policy.default projects/{project}/regions/{region}/clusters/{cluster}