Update README.md
Minor syntax tweaks for better secrets posture.
This commit is contained in:
parent
35ca8a006f
commit
0c947338ab
|
@ -162,7 +162,7 @@ gcloud iam service-accounts keys create account.json \
|
|||
|
||||
> ⚠️ **Warning**
|
||||
>
|
||||
> The `account.json` credentials gives privelleged access to this GCP project. Be sure to prevent from accidently leaking these credentials in version control systems such as `git`. In general, as an operator on your own host machine, or in your own GCP cloud shell is ok. However, using a secrets management system like HashiCorp [Vault](https://www.vaultproject.io/) can often be a better solution for teams. For this tutorial's purposes, we'll be storing the `account.json` credentials on disk in the cloud shell.
|
||||
> The `account.json` credentials gives privileged access to this GCP project. Be careful to avoid leaking these credentials by accidentally committing them to version control systems such as `git`, or storing them where they are visible to others. In general, storing these credentials on an individually operated, private computer (like your laptop) or in your own GCP cloud shell is acceptable for testing purposes. For production use, or for teams, use a secrets management system like HashiCorp [Vault](https://www.vaultproject.io/) For this tutorial's purposes, we'll be storing the `account.json` credentials on disk in the cloud shell.
|
||||
|
||||
Now set the *full path* of the newly created `account.json` file as `GOOGLE_APPLICATION_CREDENTIALS` environment variable.
|
||||
|
||||
|
@ -256,4 +256,4 @@ To destroy all the demo infrastrucure:
|
|||
|
||||
```console
|
||||
terraform destroy -force -var="project=${GOOGLE_PROJECT}" -var="credentials=${GOOGLE_APPLICATION_CREDENTIALS}"
|
||||
```
|
||||
```
|
||||
|
|
Loading…
Reference in New Issue