mirror of
https://github.com/letic/terraform-provider-google.git
synced 2024-07-08 19:18:30 +00:00
60 lines
2.1 KiB
Markdown
60 lines
2.1 KiB
Markdown
---
|
|
layout: "google"
|
|
page_title: "Google: google_kms_crypto_key_iam_binding"
|
|
sidebar_current: "docs-google-kms-crypto-key-iam-binding"
|
|
description: |-
|
|
Allows management of a single binding with an IAM policy for a Google Cloud KMS crypto key
|
|
---
|
|
|
|
# google\_kms\_crypto\_key\_iam\_binding
|
|
|
|
Allows creation and management of a single binding within IAM policy for
|
|
an existing Google Cloud KMS crypto key.
|
|
|
|
~> **Note:** On create, this resource will overwrite members of any existing roles.
|
|
Use `terraform import` and inspect the `terraform plan` output to ensure
|
|
your existing members are preserved.
|
|
|
|
## Example Usage
|
|
|
|
```hcl
|
|
resource "google_kms_crypto_key_iam_binding" "crypto_key" {
|
|
crypto_key_id = "my-gcp-project/us-central1/my-key-ring/my-crypto-key"
|
|
role = "roles/editor"
|
|
|
|
members = [
|
|
"user:alice@gmail.com",
|
|
]
|
|
}
|
|
```
|
|
|
|
## Argument Reference
|
|
|
|
The following arguments are supported:
|
|
|
|
* `members` - (Required) A list of users that the role should apply to. For more details on format and restrictions see https://cloud.google.com/billing/reference/rest/v1/Policy#Binding
|
|
|
|
* `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
|
|
`[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
|
|
`{location_name}/{key_ring_name}/{crypto_key_name}`.
|
|
In the second form, the provider's project setting will be used as a fallback.
|
|
|
|
## Attributes Reference
|
|
|
|
In addition to the arguments listed above, the following computed attributes are
|
|
exported:
|
|
|
|
* `etag` - (Computed) The etag of the crypto key'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 `crypto_key_id` and role, e.g.
|
|
|
|
```
|
|
$ terraform import google_kms_crypto_key_iam_binding.crypto_key "my-gcp-project/us-central1/my-key-ring/my-crypto-key roles/editor"
|
|
```
|