mirror of
https://github.com/letic/terraform-provider-google.git
synced 2024-10-01 16:21:06 +00:00
Fixed small typos in the doc, where the custom roles names should contain "projects|organizations" in plural form. (#1012)
This commit is contained in:
parent
250596d4d0
commit
0421710712
@ -53,7 +53,7 @@ each accept the following arguments:
|
||||
|
||||
* `role` (Required) - The role/permission that will be granted to the members.
|
||||
See the [IAM Roles](https://cloud.google.com/compute/docs/access/iam) documentation for a complete list of roles.
|
||||
Note that custom roles must be of the format `[project|organization]/{parent-name}/roles/{role-name}`.
|
||||
Note that custom roles must be of the format `[projects|organizations]/{parent-name}/roles/{role-name}`.
|
||||
|
||||
* `members` (Required) - An array of identites that will be granted the privilege in the `role`.
|
||||
Each entry can have one of the following values:
|
||||
|
@ -32,7 +32,7 @@ The following arguments are supported:
|
||||
|
||||
* `role` - (Required) The role that should be applied. Only one
|
||||
`google_kms_crypto_key_iam_binding` can be used per role. Note that custom roles must be of the format
|
||||
`[project|organization]/{parent-name}/roles/{role-name}`.
|
||||
`[projects|organizations]/{parent-name}/roles/{role-name}`.
|
||||
|
||||
* `crypto_key_id` - (Required) The crypto key ID, in the form
|
||||
`{project_id}/{location_name}/{key_ring_name}/{crypto_key_name}` or
|
||||
|
@ -33,7 +33,7 @@ The following arguments are supported:
|
||||
* `member` - (Required) The user that the role should apply to.
|
||||
|
||||
* `role` - (Required) The role that should be applied. Note that custom roles must be of the format
|
||||
`[project|organization]/{parent-name}/roles/{role-name}`.
|
||||
`[projects|organizations]/{parent-name}/roles/{role-name}`.
|
||||
|
||||
* `crypto_key_id` - (Required) The key ring ID, in the form
|
||||
`{project_id}/{location_name}/{key_ring_name}/{crypto_key_name}` or
|
||||
|
@ -80,7 +80,7 @@ The following arguments are supported:
|
||||
|
||||
* `role` - (Required) The role that should be applied. Only one
|
||||
`google_kms_key_ring_iam_binding` can be used per role. Note that custom roles must be of the format
|
||||
`[project|organization]/{parent-name}/roles/{role-name}`.
|
||||
`[projects|organizations]/{parent-name}/roles/{role-name}`.
|
||||
|
||||
* `policy_data` - (Required only by `google_kms_key_ring_iam_policy`) The policy data generated by
|
||||
a `google_iam_policy` data source.
|
||||
|
@ -36,7 +36,7 @@ The following arguments are supported:
|
||||
|
||||
* `role` - (Required) The role that should be applied. Only one
|
||||
`google_organization_iam_binding` can be used per role. Note that custom roles must be of the format
|
||||
`[project|organization]/{parent-name}/roles/{role-name}`.
|
||||
`[projects|organizations]/{parent-name}/roles/{role-name}`.
|
||||
|
||||
* `members` - (Required) A list of users that the role should apply to.
|
||||
|
||||
|
@ -32,7 +32,7 @@ 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
|
||||
`[project|organization]/{parent-name}/roles/{role-name}`.
|
||||
`[projects|organizations]/{parent-name}/roles/{role-name}`.
|
||||
|
||||
* `member` - (Required) The user that the role should apply to.
|
||||
|
||||
|
@ -41,7 +41,7 @@ The following arguments are supported:
|
||||
|
||||
* `role` - (Required) The role that should be applied. Only one
|
||||
`google_project_iam_binding` can be used per role. Note that custom roles must be of the format
|
||||
`[project|organization]/{parent-name}/roles/{role-name}`.
|
||||
`[projects|organizations]/{parent-name}/roles/{role-name}`.
|
||||
|
||||
* `project` - (Optional) The project ID. If not specified, uses the
|
||||
ID of the project configured with the provider.
|
||||
|
@ -38,7 +38,7 @@ The following arguments are supported:
|
||||
* **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. Note that custom roles must be of the format
|
||||
`[project|organization]/{parent-name}/roles/{role-name}`.
|
||||
`[projects|organizations]/{parent-name}/roles/{role-name}`.
|
||||
|
||||
* `project` - (Optional) The project ID. If not specified, uses the
|
||||
ID of the project configured with the provider.
|
||||
|
@ -79,7 +79,7 @@ The following arguments are supported:
|
||||
|
||||
* `role` - (Required) The role that should be applied. Only one
|
||||
`google_service_account_iam_binding` can be used per role. Note that custom roles must be of the format
|
||||
`[project|organization]/{parent-name}/roles/{role-name}`.
|
||||
`[projects|organizations]/{parent-name}/roles/{role-name}`.
|
||||
|
||||
* `policy_data` - (Required only by `google_service_account_iam_policy`) The policy data generated by
|
||||
a `google_iam_policy` data source.
|
||||
|
@ -75,7 +75,7 @@ The following arguments are supported:
|
||||
|
||||
* `role` - (Required) The role that should be applied. Only one
|
||||
`google_pubsub_topic_iam_binding` can be used per role. Note that custom roles must be of the format
|
||||
`[project|organization]/{parent-name}/roles/{role-name}`.
|
||||
`[projects|organizations]/{parent-name}/roles/{role-name}`.
|
||||
|
||||
* `policy_data` - (Required only by `google_pubsub_topic_iam_policy`) The policy data generated by
|
||||
a `google_iam_policy` data source.
|
||||
|
@ -54,7 +54,7 @@ The following arguments are supported:
|
||||
* **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. Note that custom roles must be of the format
|
||||
`[project|organization]/{parent-name}/roles/{role-name}`.
|
||||
`[projects|organizations]/{parent-name}/roles/{role-name}`.
|
||||
|
||||
## Attributes Reference
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user