terraform-provider-google/website/docs/r/google_kms_crypto_key_iam_member.html.markdown
James Turley 6f4a7926ba IAM resources for KMS KeyRIng and CryptoKey (#781)
* Add IAM bindings and member resources for KMS KeyRings

* Add IAM bindings and member resources for KMS CryptoKeys

* Docs for key ring and crypto key IAM resources

* Exctract KMS policy conversions to helper functions

* Split iam_binding and iam_member tests for KMS

* Docs for kms IAM member resources

* Run KMS IAM tests in own project
2017-11-23 11:26:43 -08:00

48 lines
1.5 KiB
Markdown

---
layout: "google"
page_title: "Google: google_kms_crypto_key_iam_member"
sidebar_current: "docs-google-kms-crypto-key-iam-member"
description: |-
Allows management of a single member for a single binding on the IAM policy for a Google Cloud KMS crypto key.
---
# google\_kms\_crypto\_key\_iam\_member
Allows creation and management of a single member for a single binding within
the IAM policy for an existing Google Cloud KMS crypto key.
~> **Note:** This resource _must not_ be used in conjunction with
`google_kms_crypto_key_iam_policy` or they will fight over what your policy
should be. Similarly, roles controlled by `google_kms_crypto_key_iam_binding`
should not be assigned to using `google_kms_crypto_key_iam_member`.
## Example Usage
```hcl
resource "google_kms_crypto_key_iam_member" "crypto_key" {
crypto_key_id = "your-crypto-key-id"
role = "roles/editor"
member = "user:jane@example.com"
}
```
## Argument Reference
The following arguments are supported:
* `member` - (Required) The user that the role should apply to.
* `role` - (Required) The role that should be applied.
* `crypto_key_id` - (Required) The key ring 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 project's IAM policy.