From b10bc93dcb730ea48f04941a43c666d57971478e Mon Sep 17 00:00:00 2001 From: Kosmas Chatzimichalis Date: Mon, 12 Sep 2022 16:31:24 +0200 Subject: [PATCH] Update README.md Fix type exists to exist --- operations/gcp-kms-unseal/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/operations/gcp-kms-unseal/README.md b/operations/gcp-kms-unseal/README.md index 9cc07ebe..bd6cd241 100644 --- a/operations/gcp-kms-unseal/README.md +++ b/operations/gcp-kms-unseal/README.md @@ -20,7 +20,7 @@ KMS](https://learn.hashicorp.com/vault/operations/autounseal-gcp-kms) guide. > Set the `account_file_path` to where your Cloud IAM service account file is located. This is the service account that the Terraform uses to provision GCP resources. If you do not have one, follow the [GCP documentation](https://cloud.google.com/docs/authentication/getting-started) to create a service account and download the JSON file. -1. This guide expects a Cloud KMS key ring and crypto key to already exists. If you **don't** have one to use for Vault auto-unseal, un-comment the key ring and key creation portion in the `main.tf` file. **NOTE:** Keep line 93 commented out and use line 92. +1. This guide expects a Cloud KMS key ring and crypto key to already exist. If you **don't** have one to use for Vault auto-unseal, un-comment the key ring and key creation portion in the `main.tf` file. **NOTE:** Keep line 93 commented out and use line 92. ```shell ...