From 97cc6fb4042c705cf2cc7d79e347e3e967ec5863 Mon Sep 17 00:00:00 2001 From: Tugdual Saunier Date: Thu, 1 Feb 2018 00:35:52 +0700 Subject: [PATCH] Fix wrong resource type in CryptoKey/IAM binding doc (#1030) --- .../docs/r/google_kms_crypto_key_iam_binding.html.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/docs/r/google_kms_crypto_key_iam_binding.html.markdown b/website/docs/r/google_kms_crypto_key_iam_binding.html.markdown index 0479e785..16b592b9 100644 --- a/website/docs/r/google_kms_crypto_key_iam_binding.html.markdown +++ b/website/docs/r/google_kms_crypto_key_iam_binding.html.markdown @@ -14,7 +14,7 @@ an existing Google Cloud KMS crypto key. ## Example Usage ```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" 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. ``` -$ 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" ```