» IAM policy for Service Directory Namespace

Three different resources help you manage your IAM policy for Service Directory Namespace. Each of these resources serves a different use case:

» google_service_directory_namespace_iam_policy

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

resource "google_service_directory_namespace_iam_policy" "policy" {
  name = google_service_directory_namespace.example.name
  policy_data = data.google_iam_policy.admin.policy_data
}

» google_service_directory_namespace_iam_binding

resource "google_service_directory_namespace_iam_binding" "binding" {
  name = google_service_directory_namespace.example.name
  role = "roles/viewer"
  members = [
    "user:jane@example.com",
  ]
}

» google_service_directory_namespace_iam_member

resource "google_service_directory_namespace_iam_member" "member" {
  name = google_service_directory_namespace.example.name
  role = "roles/viewer"
  member = "user:jane@example.com"
}

» Argument Reference

The following arguments are supported:

  • name - (Required) Used to find the parent resource to bind the IAM policy to

  • 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_service_directory_namespace_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_service_directory_namespace_iam_policy) The policy data generated by a google_iam_policy data source.

» Attributes Reference

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

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

» Import

For all import syntaxes, the "resource in question" can take any of the following forms:

  • projects/{{project}}/locations/{{location}}/namespaces/{{namespace_id}}
  • {{project}}/{{location}}/{{namespace_id}}
  • {{location}}/{{namespace_id}}

Any variables not passed in the import command will be taken from the provider configuration.

Service Directory namespace IAM resources can be imported using the resource identifiers, role, and member.

IAM member imports use space-delimited identifiers: the resource in question, the role, and the member identity, e.g. $ terraform import google_service_directory_namespace_iam_member.editor "projects/{{project}}/locations/{{location}}/namespaces/{{namespace_id}} roles/viewer user:jane@example.com"

IAM binding imports use space-delimited identifiers: the resource in question and the role, e.g. $ terraform import google_service_directory_namespace_iam_binding.editor "projects/{{project}}/locations/{{location}}/namespaces/{{namespace_id}} roles/viewer"

IAM policy imports use the identifier of the resource in question, e.g. $ terraform import google_service_directory_namespace_iam_policy.editor projects/{{project}}/locations/{{location}}/namespaces/{{namespace_id}}