Three different resources help you manage your IAM policy for Healthcare dataset. Each of these resources serves a different use case:
google_healthcare_dataset_iam_policy
: Authoritative. Sets the IAM policy for the dataset and replaces any existing policy already attached.google_healthcare_dataset_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 dataset are preserved.google_healthcare_dataset_iam_member
: Non-authoritative. Updates the IAM policy to grant a role to a new member. Other members for the role for the dataset are preserved.data "google_iam_policy" "admin" {
binding {
role = "roles/editor"
members = [
"user:jane@example.com",
]
}
}
resource "google_healthcare_dataset_iam_policy" "dataset" {
dataset_id = "your-dataset-id"
policy_data = data.google_iam_policy.admin.policy_data
}
resource "google_healthcare_dataset_iam_binding" "dataset" {
dataset_id = "your-dataset-id"
role = "roles/editor"
members = [
"user:jane@example.com",
]
}
resource "google_healthcare_dataset_iam_member" "dataset" {
dataset_id = "your-dataset-id"
role = "roles/editor"
member = "user:jane@example.com"
}
The following arguments are supported:
dataset_id
- (Required) The dataset ID, in the form
{project_id}/{location_name}/{dataset_name}
or
{location_name}/{dataset_name}
. In the second form, the provider's
project setting will be used as a fallback.
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_healthcare_dataset_iam_binding
can be used per role. Note that custom roles must be of the format
[projects|organizations]/{parent-name}/roles/{role-name}
.
policy_data
- (Required only by google_healthcare_dataset_iam_policy
) The policy data generated by
a google_iam_policy
data source.
In addition to the arguments listed above, the following computed attributes are exported:
etag
- (Computed) The etag of the dataset's IAM policy.IAM member imports use space-delimited identifiers that contains the dataset_id
, role
, and member
. For example:
"{{project_id}}/{{location}}/{{dataset}} roles/editor jane@example.com"
An import
block (Terraform v1.5.0 and later) can be used to import IAM members:
import {
id = "{{project_id}}/{{location}}/{{dataset}} roles/editor jane@example.com"
to = google_healthcare_dataset_iam_member.default
}
The terraform import
command can also be used:
$ terraform import google_healthcare_dataset_iam_member.default "{{project_id}}/{{location}}/{{dataset}} roles/editor jane@example.com"
IAM binding imports use space-delimited identifiers that contain the resource's dataset_id
and role
. For example:
"{{project_id}}/{{location}}/{{dataset}} roles/editor"
An import
block (Terraform v1.5.0 and later) can be used to import IAM bindings:
import {
id = "{{project_id}}/{{location}}/{{dataset}} roles/editor"
to = google_healthcare_dataset_iam_binding.default
}
The terraform import
command can also be used:
$ terraform import google_healthcare_dataset_iam_binding.default "{{project_id}}/{{location}}/{{dataset}} roles/editor"
IAM policy imports use the identifier of the Healthcase Dataset resource. For example:
"{{project_id}}/{{location}}/{{dataset}}"
An import
block (Terraform v1.5.0 and later) can be used to import IAM policies:
import {
id = "{{project_id}}/{{location}}/{{dataset}}"
to = google_healthcare_dataset_iam_policy.default
}
The terraform import
command can also be used:
$ terraform import google_healthcare_dataset_iam_policy.default {{project_id}}/{{location}}/{{dataset}}