From d6cfe93c7aac148a8715b5c506d404c533f15921 Mon Sep 17 00:00:00 2001 From: buildmaster Date: Fri, 20 Oct 2017 15:43:03 +0000 Subject: [PATCH] Sync docs from 2.0.x to gh-pages --- .../multi/multi_vault.config.backends.database-backends.html | 5 ++++- 2.0.x/single/spring-cloud-vault.html | 5 ++++- 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/2.0.x/multi/multi_vault.config.backends.database-backends.html b/2.0.x/multi/multi_vault.config.backends.database-backends.html index 1147e044..3eefe321 100644 --- a/2.0.x/multi/multi_vault.config.backends.database-backends.html +++ b/2.0.x/multi/multi_vault.config.backends.database-backends.html @@ -6,7 +6,10 @@ services that need to access a database no longer need to configure credentials: they can request them from Vault, and use Vault’s leasing mechanism to more easily roll keys.

Spring Cloud Vault integrates with these backends:

Using a database secret backend requires to enable the backend in the configuration and the spring-cloud-vault-config-databases -dependency.

Example 5.1. pom.xml

<dependencies>
+dependency.
Vault ships since 0.7.1 with a dedicated database secret backend that allows
+database integration via plugins. You can use that specific backend by adapting
+one of the JDBC database properties above. Make sure to specify the appropriate
+backend path, e.g. spring.cloud.vault.mysql.role.backend=database.
Example 5.1. pom.xml
<dependencies>
     <dependency>
         <groupId>org.springframework.cloud</groupId>
         <artifactId>spring-cloud-vault-config-databases</artifactId>
diff --git a/2.0.x/single/spring-cloud-vault.html b/2.0.x/single/spring-cloud-vault.html
index 619b96cc..29704e52 100644
--- a/2.0.x/single/spring-cloud-vault.html
+++ b/2.0.x/single/spring-cloud-vault.html
@@ -290,7 +290,10 @@ services that need to access a database no longer need to configure
 credentials: they can request them from Vault, and use Vault’s leasing
 mechanism to more easily roll keys.
Spring Cloud Vault integrates with these backends:
Using a database secret backend requires to enable the
 backend in the configuration and the spring-cloud-vault-config-databases
-dependency.
Example 5.1. pom.xml
<dependencies>
+dependency.
Vault ships since 0.7.1 with a dedicated database secret backend that allows
+database integration via plugins. You can use that specific backend by adapting
+one of the JDBC database properties above. Make sure to specify the appropriate
+backend path, e.g. spring.cloud.vault.mysql.role.backend=database.
Example 5.1. pom.xml
<dependencies>
     <dependency>
         <groupId>org.springframework.cloud</groupId>
         <artifactId>spring-cloud-vault-config-databases</artifactId>