From 8006becc498b6b11133eb05db32223f3dfa5a691 Mon Sep 17 00:00:00 2001 From: buildmaster Date: Wed, 13 Feb 2019 13:50:12 +0000 Subject: [PATCH] Sync docs from master to gh-pages --- multi/multi__client_side_usage.html | 2 +- multi/multi_vault-lease-renewal.html | 5 ++++- ...i_vault.config.backends.database-backends.html | 2 +- multi/multi_vault.config.backends.html | 6 +++--- single/spring-cloud-vault.html | 15 +++++++++------ spring-cloud-vault.html | 2 +- 6 files changed, 19 insertions(+), 13 deletions(-) diff --git a/multi/multi__client_side_usage.html b/multi/multi__client_side_usage.html index 6c708a74..ad08ba37 100644 --- a/multi/multi__client_side_usage.html +++ b/multi/multi__client_side_usage.html @@ -13,7 +13,7 @@ the test cases). Example Maven configuration:

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-vault-config</artifactId> - <version>2.1.1.BUILD-SNAPSHOT</version> + <version>2.2.0.BUILD-SNAPSHOT</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> diff --git a/multi/multi_vault-lease-renewal.html b/multi/multi_vault-lease-renewal.html index 7b7255f8..0d2524eb 100644 --- a/multi/multi_vault-lease-renewal.html +++ b/multi/multi_vault-lease-renewal.html @@ -19,4 +19,7 @@ to false. This is not recommended as leases can exp Spring Cloud Vault cannot longer access Vault or services using generated credentials and valid credentials remain active after application shutdown.

spring.cloud.vault:
-    config.lifecycle.enabled: true

See also: Vault Documentation: Lease, Renew, and Revoke

Prev   
9. Vault Client SSL configuration Home 
\ No newline at end of file + config.lifecycle: + enabled: true + min-renewal: 10s + expiry-threshold: 1m

See also: Vault Documentation: Lease, Renew, and Revoke

Prev   
9. Vault Client SSL configuration Home 
\ No newline at end of file diff --git a/multi/multi_vault.config.backends.database-backends.html b/multi/multi_vault.config.backends.database-backends.html index d813b881..6bca30f0 100644 --- a/multi/multi_vault.config.backends.database-backends.html +++ b/multi/multi_vault.config.backends.database-backends.html @@ -13,7 +13,7 @@ backend path, e.g. spring.cloud.vault.mysql.role.backend=d <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-databases</artifactId> - <version>2.1.1.BUILD-SNAPSHOT</version> + <version>2.2.0.BUILD-SNAPSHOT</version> </dependency> </dependencies>
[Note]Note

Enabling multiple JDBC-compliant databases will generate credentials and store them by default in the same property keys hence property names for diff --git a/multi/multi_vault.config.backends.html b/multi/multi_vault.config.backends.html index 9ccc1b7a..6fa9618e 100644 --- a/multi/multi_vault.config.backends.html +++ b/multi/multi_vault.config.backends.html @@ -46,7 +46,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-consul</artifactId> - <version>2.1.1.BUILD-SNAPSHOT</version> + <version>2.2.0.BUILD-SNAPSHOT</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.consul.enabled=true (default false) and @@ -63,7 +63,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-rabbitmq</artifactId> - <version>2.1.1.BUILD-SNAPSHOT</version> + <version>2.2.0.BUILD-SNAPSHOT</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.rabbitmq.enabled=true (default false) @@ -82,7 +82,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-aws</artifactId> - <version>2.1.1.BUILD-SNAPSHOT</version> + <version>2.2.0.BUILD-SNAPSHOT</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.aws=true (default false) diff --git a/single/spring-cloud-vault.html b/single/spring-cloud-vault.html index d6c28c01..dcc70975 100644 --- a/single/spring-cloud-vault.html +++ b/single/spring-cloud-vault.html @@ -47,7 +47,7 @@ the test cases). Example Maven configuration:

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-vault-config</artifactId> - <version>2.1.1.BUILD-SNAPSHOT</version> + <version>2.2.0.BUILD-SNAPSHOT</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> @@ -339,7 +339,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-consul</artifactId> - <version>2.1.1.BUILD-SNAPSHOT</version> + <version>2.2.0.BUILD-SNAPSHOT</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.consul.enabled=true (default false) and @@ -356,7 +356,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-rabbitmq</artifactId> - <version>2.1.1.BUILD-SNAPSHOT</version> + <version>2.2.0.BUILD-SNAPSHOT</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.rabbitmq.enabled=true (default false) @@ -375,7 +375,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-aws</artifactId> - <version>2.1.1.BUILD-SNAPSHOT</version> + <version>2.2.0.BUILD-SNAPSHOT</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.aws=true (default false) @@ -402,7 +402,7 @@ backend path, e.g. spring.cloud.vault.mysql.role.backend=d <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-databases</artifactId> - <version>2.1.1.BUILD-SNAPSHOT</version> + <version>2.2.0.BUILD-SNAPSHOT</version> </dependency> </dependencies>

[Note]Note

Enabling multiple JDBC-compliant databases will generate credentials and store them by default in the same property keys hence property names for @@ -552,4 +552,7 @@ to false. This is not recommended as leases can exp Spring Cloud Vault cannot longer access Vault or services using generated credentials and valid credentials remain active after application shutdown.

spring.cloud.vault:
-    config.lifecycle.enabled: true

See also: Vault Documentation: Lease, Renew, and Revoke

\ No newline at end of file + config.lifecycle: + enabled: true + min-renewal: 10s + expiry-threshold: 1m
  • 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.

See also: Vault Documentation: Lease, Renew, and Revoke

\ No newline at end of file diff --git a/spring-cloud-vault.html b/spring-cloud-vault.html index 4e5a358a..b552267d 100644 --- a/spring-cloud-vault.html +++ b/spring-cloud-vault.html @@ -90,7 +90,7 @@ $(addBlockSwitches);
-

2.1.1.BUILD-SNAPSHOT

+

2.2.0.BUILD-SNAPSHOT