Fix wrong resource type in CryptoKey/IAM binding doc (#1030)

This commit is contained in:
Tugdual Saunier 2018-02-01 00:35:52 +07:00 committed by Vincent Roseberry
parent ce74ccca07
commit 97cc6fb404

View File

@ -14,7 +14,7 @@ an existing Google Cloud KMS crypto key.
## Example Usage ## Example Usage
```hcl ```hcl
resource "google_kms_crypto_key_binding" "crypto_key" { resource "google_kms_crypto_key_iam_binding" "crypto_key" {
crypto_key_id = "your-crypto-key-id" crypto_key_id = "your-crypto-key-id"
role = "roles/editor" role = "roles/editor"
@ -51,5 +51,5 @@ exported:
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. 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_binding.my_binding "your-project-id/location-name/key-name roles/viewer" $ terraform import google_kms_crypto_key_iam_binding.my_binding "your-project-id/location-name/key-name roles/viewer"
``` ```