Merge branch '2.5.x'
This commit is contained in:
commit
ad8ce2aa05
|
|
@ -143,7 +143,7 @@ If `spring.config.location` contains directories (as opposed to files), they sho
|
||||||
At runtime they will be appended with the names generated from `spring.config.name` before being loaded.
|
At runtime they will be appended with the names generated from `spring.config.name` before being loaded.
|
||||||
Files specified in `spring.config.location` are imported directly.
|
Files specified in `spring.config.location` are imported directly.
|
||||||
|
|
||||||
NOTE: Both directory and file location values are also expanded to check for <<boot-features-external-config-files-profile-specific,profile-specific files>>.
|
NOTE: Both directory and file location values are also expanded to check for <<features#features.external-config.files.profile-specific,profile-specific files>>.
|
||||||
For example, if you have a `spring.config.location` of `classpath:myconfig.properties`, you will also find appropriate `classpath:myconfig-<profile>.properties` files are loaded.
|
For example, if you have a `spring.config.location` of `classpath:myconfig.properties`, you will also find appropriate `classpath:myconfig-<profile>.properties` files are loaded.
|
||||||
|
|
||||||
In most situations, each configprop:spring.config.location[] item you add will reference a single file or directory.
|
In most situations, each configprop:spring.config.location[] item you add will reference a single file or directory.
|
||||||
|
|
@ -154,7 +154,7 @@ If you have a complex location setup, and you use profile-specific configuration
|
||||||
A location group is a collection of locations that are all considered at the same level.
|
A location group is a collection of locations that are all considered at the same level.
|
||||||
For example, you might want to group all classpath locations, then all external locations.
|
For example, you might want to group all classpath locations, then all external locations.
|
||||||
Items within a location group should be separated with `;`.
|
Items within a location group should be separated with `;`.
|
||||||
See the example in the "`<<features.external-config.files.profile-specific>>`" section for more details.
|
See the example in the "`<<features#features.external-config.files.profile-specific>>`" section for more details.
|
||||||
|
|
||||||
Locations configured by using `spring.config.location` replace the default locations.
|
Locations configured by using `spring.config.location` replace the default locations.
|
||||||
For example, if `spring.config.location` is configured with the value `optional:classpath:/custom-config/,optional:file:./custom-config/`, the complete set of locations considered is:
|
For example, if `spring.config.location` is configured with the value `optional:classpath:/custom-config/,optional:file:./custom-config/`, the complete set of locations considered is:
|
||||||
|
|
@ -230,7 +230,7 @@ For example, if profiles `prod,live` are specified by the configprop:spring.prof
|
||||||
|
|
||||||
[NOTE]
|
[NOTE]
|
||||||
====
|
====
|
||||||
The last-wins strategy applies at the <<features.external-config.files.location-groups,location group>> level.
|
The last-wins strategy applies at the <<features#features.external-config.files.location-groups,location group>> level.
|
||||||
A configprop:spring.config.location[] of `classpath:/cfg/,classpath:/ext/` will not have the same override rules as `classpath:/cfg/;classpath:/ext/`.
|
A configprop:spring.config.location[] of `classpath:/cfg/,classpath:/ext/` will not have the same override rules as `classpath:/cfg/;classpath:/ext/`.
|
||||||
|
|
||||||
For example, continuing our `prod,live` example above, we might have the following files:
|
For example, continuing our `prod,live` example above, we might have the following files:
|
||||||
|
|
@ -312,7 +312,7 @@ In both of the above examples, the values from the `my.properties` file will tak
|
||||||
Several locations can be specified under a single `spring.config.import` key.
|
Several locations can be specified under a single `spring.config.import` key.
|
||||||
Locations will be processed in the order that they are defined, with later imports taking precedence.
|
Locations will be processed in the order that they are defined, with later imports taking precedence.
|
||||||
|
|
||||||
NOTE: When appropriate, <<boot-features-external-config-files-profile-specific, Profile-specific variants>> are also considered for import.
|
NOTE: When appropriate, <<features#features.external-config.files.profile-specific, Profile-specific variants>> are also considered for import.
|
||||||
The example above would import both `my.properties` as well as any `my-<profile>.properties` variants.
|
The example above would import both `my.properties` as well as any `my-<profile>.properties` variants.
|
||||||
|
|
||||||
[TIP]
|
[TIP]
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue