upstream/vault
1
0
Fork 0
mirror of https://github.com/hashicorp/vault.git synced 2026-05-28 04:10:44 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

fix docs (#4466)

Browse source
This commit is contained in:
emily 2018-04-26 13:54:19 -07:00 committed by Jeff Mitchell
parent da98217e61
commit 462f98673f
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
website/source/docs/secrets/gcp/index.html.md
View file

@ -59,12 +59,12 @@ Success! Enabled the gcp secrets engine at: gcp/
You will need to set up the secrets engine with:
* **[Config](#config)**: General config, including credentials that Vault will need to make calls
to GCP APIs (either explicitly or using Application Default Credentials), lease defaults, etc. Example:
to GCP APIs (either explicitly or using Application Default Credentials), lease defaults, etc.
* **[Rolesets](#rolesets)**: Generated credentials will need to be associated with sets of
[IAM roles](https://cloud.google.com/iam/docs/understanding-roles) on specific GCP resources. Rolesets
have an associated `secret_type` that determines a secret type that can be generated
under this role set. Example:
under this role set.
### Usage - Secret Generation