Skip to content

Fix typo #411

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Fix typo #411

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b10bc93
Update README.md
Kosmas Sep 12, 2022
284e6c2
Merge pull request #1 from Kosmas/fix-typo
Kosmas Sep 12, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion operations/gcp-kms-unseal/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
...
Expand Down