google_folder_iam_binding

Allows creation and management of a single binding within IAM policy for an existing Google Cloud Platform folder.

Note: This resource must not be used in conjunction with google_folder_iam_policy or they will fight over what your policy should be.

Example Usage

resource "google_folder" "department1" {
  display_name = "Department 1"
  parent       = "organizations/1234567"
}

resource "google_folder_iam_binding" "admin" {
  folder  = "${google_folder.department1.name}"
  role    = "roles/editor"

  members = [
    "user:[email protected]",
  ]
}

Argument Reference

The following arguments are supported:

• folder - (Required) The resource name of the folder the policy is attached to. Its format is folders/{folder_id}.

• members (Required) - An array of identites that will be granted the privilege in the role. Each entry can have one of the following values:

  • user:{emailid}: An email address that represents a specific Google account. For example, [email protected] or [email protected].
  • serviceAccount:{emailid}: An email address that represents a service account. For example, [email protected].
  • group:{emailid}: An email address that represents a Google group. For example, [email protected].
  • domain:{domain}: A Google Apps domain 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_folder_iam_binding can be used per role. Note that custom roles must be of the format [projects|organizations]/{parent-name}/roles/{role-name}.

Attributes Reference

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

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

Import

IAM binding imports use space-delimited identifiers; first the resource in question and then the role. These bindings can be imported using the folder and role, e.g.

$ terraform import google_folder_iam_binding.viewer "folder-name roles/viewer"