Add consistency for for IAM imports. - Adds imports for projects, folders, crypto keys, organizations, and key rings. - Anything else with IAM can implement a simple method and begin working immediately. - Add tests for all the IAM imports. - Import documentation for IAM resources.
1.6 KiB
layout | page_title | sidebar_current | description |
---|---|---|---|
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:jane@example.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. -
member
- (Required) The user that the role should apply to.
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 account e.g.
$ terraform import google_organization_iam_member.my_org "your-org-id roles/viewer foo@example.com"