SpringCloud/spring-cloud-vault
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add configurable endpoints for renew and revoke of secret leases.

Browse Source 
We now allow configuration which endpoints to use for renew/revocation
through configuring spring.cloud.vault.config.lifecycle.lease-endpoints=Legacy/SysLeases.

Vault 0.8 has introduced endpoints below sys/leases and deprecated the previous legacy approach.

Original pull request: gh-334.
This commit is contained in:
Mårten Svantesson
2019-05-14 12:15:16 +02:00
committed by Mark Paluch
parent df0c557666
commit 59091bb7c4
4 changed files with 31 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/src/main/asciidoc/spring-cloud-vault.adoc
View File

@@ -1308,6 +1308,7 @@ spring.cloud.vault:
enabled: true
min-renewal: 10s
expiry-threshold: 1m
lease-endpoints: Legacy
----
====
@@ -1315,5 +1316,6 @@ spring.cloud.vault:
* `enabled` controls whether leases associated with secrets are considered to be renewed and expired secrets are rotated. Enabled by default.
* `min-renewal` sets the duration that is at least required before renewing a lease. This setting prevents renewals from happening too often.
* `expiry-threshold` sets the expiry threshold. A lease is renewed the configured period of time before it expires.
* `lease-endpoints` sets the endpoints for renew and revoke. Legacy for vault versions before 0.8 and SysLeases for later.
See also: https://www.vaultproject.io/docs/concepts/lease.html[Vault Documentation: Lease, Renew, and Revoke]