Skip to content

Commit 97cc6fb

Browse files
tucksaunrosbo
authored andcommitted
Fix wrong resource type in CryptoKey/IAM binding doc (#1030)
1 parent ce74ccc commit 97cc6fb

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

website/docs/r/google_kms_crypto_key_iam_binding.html.markdown

+2-2
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ an existing Google Cloud KMS crypto key.
1414
## Example Usage
1515

1616
```hcl
17-
resource "google_kms_crypto_key_binding" "crypto_key" {
17+
resource "google_kms_crypto_key_iam_binding" "crypto_key" {
1818
crypto_key_id = "your-crypto-key-id"
1919
role = "roles/editor"
2020
@@ -51,5 +51,5 @@ exported:
5151
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.
5252

5353
```
54-
$ terraform import google_kms_crypto_key_binding.my_binding "your-project-id/location-name/key-name roles/viewer"
54+
$ terraform import google_kms_crypto_key_iam_binding.my_binding "your-project-id/location-name/key-name roles/viewer"
5555
```

0 commit comments

Comments
 (0)