diff --git a/reference/html/index.html b/reference/html/index.html index 03bec018..88a86a5b 100644 --- a/reference/html/index.html +++ b/reference/html/index.html @@ -1232,8 +1232,17 @@ All of the properties in the preceding table must be prefixed with spring.

All configurable properties can be found in org.springframework.cloud.config.server.environment.VaultEnvironmentProperties.

-
-

Vault 0.10.0 introduced a versioned key-value backend (k/v backend version 2) that exposes a different API than earlier versions, it now requires a data/ between the mount path and the actual context path and wraps secrets in a data object. Setting kvVersion=2 will take this into account.

+
+ + + + + +
+ + +Vault 0.10.0 introduced a versioned key-value backend (k/v backend version 2) that exposes a different API than earlier versions, it now requires a data/ between the mount path and the actual context path and wraps secrets in a data object. Setting spring.cloud.config.server.vault.kv-version=2 will take this into account. +

Optionally, there is support for the Vault Enterprise X-Vault-Namespace header. To have it sent to Vault set the namespace property.

diff --git a/reference/html/spring-cloud-config.html b/reference/html/spring-cloud-config.html index 03bec018..88a86a5b 100644 --- a/reference/html/spring-cloud-config.html +++ b/reference/html/spring-cloud-config.html @@ -1232,8 +1232,17 @@ All of the properties in the preceding table must be prefixed with spring.

All configurable properties can be found in org.springframework.cloud.config.server.environment.VaultEnvironmentProperties.

-
-

Vault 0.10.0 introduced a versioned key-value backend (k/v backend version 2) that exposes a different API than earlier versions, it now requires a data/ between the mount path and the actual context path and wraps secrets in a data object. Setting kvVersion=2 will take this into account.

+
+ + + + + +
+ + +Vault 0.10.0 introduced a versioned key-value backend (k/v backend version 2) that exposes a different API than earlier versions, it now requires a data/ between the mount path and the actual context path and wraps secrets in a data object. Setting spring.cloud.config.server.vault.kv-version=2 will take this into account. +

Optionally, there is support for the Vault Enterprise X-Vault-Namespace header. To have it sent to Vault set the namespace property.