Add support for ReactiveDiscoveryClient
ReactiveDiscoveryClient beans are now used to configure ReactiveVaultEndpointProvider. If no ReactiveDiscoveryClient is available, then VaultEndpointProvider gets adapted by offloading the call to a worker Scheduler to avoid blocking calls on the calling thread. Resolves gh-486.
This commit is contained in:
@@ -8,3 +8,4 @@ This section briefly covers items that are new and noteworthy in the latest rele
|
||||
* Migration of `PropertySource` initialization from Spring Cloud's Bootstrap Context to Spring Boot's <<vault.configdata,ConfigData API>>.
|
||||
* Support for the <<vault.config.backends.couchbase>> backend.
|
||||
* Configuration of keystore/truststore types through `spring.cloud.vault.ssl.key-store-type=…`/`spring.cloud.vault.ssl.trust-store-type=…` including PEM support.
|
||||
* Support for `ReactiveDiscoveryClient` by configuring a `ReactiveVaultEndpointProvider`.
|
||||
|
||||
Reference in New Issue
Block a user