upstream/vault
1
0
Fork 0
mirror of https://github.com/hashicorp/vault.git synced 2026-06-10 09:22:06 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 9

fix broken link (#4329)

Browse source
This commit is contained in:
Matthew Irish 2018-04-10 11:11:38 -05:00 committed by GitHub
parent 8569e6a143
commit e7801faf2a
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
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

@ -77,7 +77,7 @@ Once the secrets engine has been set up, you can generate two types of secrets i
[IAM service account keys](https://cloud.google.com/iam/docs/service-accounts#service_account_keys).
Each secret is associated with a [Vault lease](docs/concepts/lease.html) that
Each secret is associated with a [Vault lease](/docs/concepts/lease.html) that
can be revoked and possibly renewed (see lease docs for how to do so). On revoking
a lease, the secret is no longer guaranteed to work.
@ -587,4 +587,4 @@ you run into. It could be that the API is a non-standard form or we need to re-g
## API
The GCP secrets engine has a full HTTP API. Please see the [GCP secrets engine API docs](/api/secret/gcp/index.html)
for more details.
for more details.