terraform-provider-google/website/docs/r/google_organization_iam_member.md
The Magician 5845ae4d38 Fix documentation around iam member imports (#2865)
Signed-off-by: Modular Magician <magic-modules@google.com>
2019-01-11 17:23:56 -08:00

1.8 KiB

layout page_title sidebar_current description
google Google: google_organization_iam_member docs-google-organization-iam-member Allows management of a single member for a single binding on the IAM policy for a Google Cloud Platform Organization.

google_organization_iam_member

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

~> Note: This resource must not be used in conjunction with google_organization_iam_binding for the same role or they will fight over what your policy should be.

Example Usage

resource "google_organization_iam_member" "binding" {
  org_id = "0123456789"
  role    = "roles/editor"
  member  = "user:alice@gmail.com"
}

Argument Reference

The following arguments are supported:

  • org_id - (Required) The numeric ID of the organization in which you want to create a custom role.

  • role - (Required) The role that should be applied. Note that custom roles must be of the format [projects|organizations]/{parent-name}/roles/{role-name}.

  • member - (Required) The user that the role should apply to. For more details on format and restrictions see https://cloud.google.com/billing/reference/rest/v1/Policy#Binding

Attributes Reference

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

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

Import

IAM member imports use space-delimited identifiers; the resource in question, the role, and the account. This member resource can be imported using the org_id, role, and member identity, e.g.

$ terraform import google_organization_iam_member.my_org "your-org-id roles/viewer user:foo@example.com"