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

Explain current generic secret backend lease behavior in documentation.

Browse Source 
See gh-68.
This commit is contained in:
Mark Paluch
2017-04-07 17:38:51 +02:00
parent a9c2cf72f8
commit c0150cf608
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
src/main/asciidoc/reference/getting-started.adoc
View File

@@ -483,6 +483,8 @@ public class AppConfig {
---- ----
==== ====
NOTE: Secrets obtained from `generic` secret backends are associated with a TTL (`refresh_interval`) but not a lease Id. Spring Vault's ``PropertySource`` is not refreshing/flushing these secrets once the TTL expires despite the requested `Renewal` mode.
In certain situations, it may not be possible or practical to tightly control In certain situations, it may not be possible or practical to tightly control
property source ordering when using `@VaultPropertySource` annotations. property source ordering when using `@VaultPropertySource` annotations.
For example, if the `@Configuration` classes above were registered via For example, if the `@Configuration` classes above were registered via