From 72bfe878b4241430bd78b99c05fe7150e2582d0d Mon Sep 17 00:00:00 2001 From: Mark Paluch Date: Thu, 2 Mar 2023 14:10:27 +0100 Subject: [PATCH] Revise bootstrap context guidance. Closes gh-662 --- docs/src/main/asciidoc/config-data.adoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/src/main/asciidoc/config-data.adoc b/docs/src/main/asciidoc/config-data.adoc index b58e08f3a..4d8718476 100644 --- a/docs/src/main/asciidoc/config-data.adoc +++ b/docs/src/main/asciidoc/config-data.adoc @@ -7,7 +7,8 @@ Spring Cloud Vault uses as of version 3.0 the ConfigData API to mount Vault's se In previous versions, the Bootstrap context was used. The ConfigData API is much more flexible as it allows specifying which configuration systems to import and in which order. -NOTE: You can enable the deprecated bootstrap context either by setting the configuration property `spring.cloud.bootstrap.enabled=true` or by including the dependency `org.springframework.cloud:spring-cloud-starter-bootstrap`. +NOTE: You can enable the bootstrap context either by setting the configuration property `spring.cloud.bootstrap.enabled=true` or by including the dependency `org.springframework.cloud:spring-cloud-starter-bootstrap`. +Using the boostrap context should be only rarely required hence we recommend using the Config Data API for more flexibility regarding property source ordering. [[vault.configdata.locations]] === ConfigData Locations