From f5aeed3b34dbac312669fce1044c068660bc067f Mon Sep 17 00:00:00 2001 From: buildmaster Date: Wed, 29 Jan 2020 01:21:39 +0000 Subject: [PATCH] Sync docs from master to gh-pages --- reference/html/index.html | 8 ++++++-- reference/html/spring-cloud-commons.html | 8 ++++++-- 2 files changed, 12 insertions(+), 4 deletions(-) diff --git a/reference/html/index.html b/reference/html/index.html index b03c4292..8347c27c 100644 --- a/reference/html/index.html +++ b/reference/html/index.html @@ -326,8 +326,12 @@ Thus, sibling contexts (in particular) do not need to have the same profiles or

1.3. Changing the Location of Bootstrap Properties

-

You can specify the bootstrap.yml (or .properties) location by setting spring.cloud.bootstrap.name (default: bootstrap) or spring.cloud.bootstrap.location (default: empty) — for example, in system properties. -Those properties behave like the spring.config.* variants with the same name. +

The bootstrap.yml (or .properties) location can be specified by setting spring.cloud.bootstrap.name (default: bootstrap), spring.cloud.bootstrap.location (default: empty) or spring.cloud.bootstrap.additional-location (default: empty) — for example, in System properties.

+
+
+

Those properties behave like the spring.config.* variants with the same name. +With spring.cloud.bootstrap.location the default locations are replaced and only the specified ones are used. +To add locations to the list of default ones, spring.cloud.bootstrap.additional-location could be used. In fact, they are used to set up the bootstrap ApplicationContext by setting those properties in its Environment. If there is an active profile (from spring.profiles.active or through the Environment API in the context you are building), properties in that profile get loaded as well, the same as in a regular Spring Boot app — for example, from bootstrap-development.properties for a development profile.

diff --git a/reference/html/spring-cloud-commons.html b/reference/html/spring-cloud-commons.html index b03c4292..8347c27c 100644 --- a/reference/html/spring-cloud-commons.html +++ b/reference/html/spring-cloud-commons.html @@ -326,8 +326,12 @@ Thus, sibling contexts (in particular) do not need to have the same profiles or

1.3. Changing the Location of Bootstrap Properties

-

You can specify the bootstrap.yml (or .properties) location by setting spring.cloud.bootstrap.name (default: bootstrap) or spring.cloud.bootstrap.location (default: empty) — for example, in system properties. -Those properties behave like the spring.config.* variants with the same name. +

The bootstrap.yml (or .properties) location can be specified by setting spring.cloud.bootstrap.name (default: bootstrap), spring.cloud.bootstrap.location (default: empty) or spring.cloud.bootstrap.additional-location (default: empty) — for example, in System properties.

+
+
+

Those properties behave like the spring.config.* variants with the same name. +With spring.cloud.bootstrap.location the default locations are replaced and only the specified ones are used. +To add locations to the list of default ones, spring.cloud.bootstrap.additional-location could be used. In fact, they are used to set up the bootstrap ApplicationContext by setting those properties in its Environment. If there is an active profile (from spring.profiles.active or through the Environment API in the context you are building), properties in that profile get loaded as well, the same as in a regular Spring Boot app — for example, from bootstrap-development.properties for a development profile.