Three different resources help you manage your IAM policy for a Spanner instance. Each of these resources serves a different use case:
google_spanner_instance_iam_policy
: Authoritative. Sets the IAM policy for the instance and replaces any existing policy already attached.google_spanner_instance_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 instance are preserved.google_spanner_instance_iam_member
: Non-authoritative. Updates the IAM policy to grant a role to a new member. Other members for the role for the instance are preserved.data "google_iam_policy" "admin" {
binding {
role = "roles/editor"
members = [
"user:jane@example.com",
]
}
}
resource "google_spanner_instance_iam_policy" "instance" {
instance = "your-instance-name"
policy_data = data.google_iam_policy.admin.policy_data
}
resource "google_spanner_instance_iam_binding" "instance" {
instance = "your-instance-name"
role = "roles/spanner.databaseAdmin"
members = [
"user:jane@example.com",
]
}
resource "google_spanner_instance_iam_member" "instance" {
instance = "your-instance-name"
role = "roles/spanner.databaseAdmin"
member = "user:jane@example.com"
}
The following arguments are supported:
instance
- (Required) The name of the instance.
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_spanner_instance_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_spanner_instance_iam_policy
) The policy data generated by
a google_iam_policy
data source.
project
- (Optional) The ID of the project in which the resource belongs. If it
is not provided, the provider project is used.
In addition to the arguments listed above, the following computed attributes are exported:
etag
- (Computed) The etag of the instance's IAM policy.IAM member imports use space-delimited identifiers that contains the instance
, role
, and member
. For example:
"{{project}}/{{instance}} roles/viewer user:foo@example.com"
An import
block (Terraform v1.5.0 and later) can be used to import IAM members:
import {
id = "{{project}}/{{instance}} roles/viewer user:foo@example.com"
to = google_spanner_instance_iam_member.default
}
The terraform import
command can also be used:
$ terraform import google_spanner_instance_iam_member.default "{{project}}/{{instance}} roles/viewer user:foo@example.com"
IAM binding imports use space-delimited identifiers that contain the resource's instance
and role
. For example:
"{{project}}/{{instance}} roles/viewer"
An import
block (Terraform v1.5.0 and later) can be used to import IAM bindings:
import {
id = "{{project}}/{{instance}} roles/viewer"
to = google_spanner_instance_iam_binding.default
}
The terraform import
command can also be used:
$ terraform import google_spanner_instance_iam_binding.default "{{project}}/{{instance}} roles/viewer"
IAM policy imports use the identifier of the Spanner Instances resource . For example:
{{project}}/{{instance}}
An import
block (Terraform v1.5.0 and later) can be used to import IAM policies:
import {
id = {{project}}/{{instance}}
to = google_spanner_instance_iam_policy.default
}
The terraform import
command can also be used:
$ terraform import google_spanner_instance_iam_policy.default {{project}}/{{instance}}