Add a tip about actuator endpoints

Update the "Externalized Configuration" section with a tip that about
the actuator `env` and `configprops` endpoints.

See gh-24336
pull/25129/head
Wesley Ugang 4 years ago committed by Phillip Webb
parent a4e6a3cfd0
commit 6ced1d7f4e

@ -496,6 +496,9 @@ On your application classpath (for example, inside your jar) you can have an `ap
When running in a new environment, an `application.properties` file can be provided outside of your jar that overrides the `name`. When running in a new environment, an `application.properties` file can be provided outside of your jar that overrides the `name`.
For one-off testing, you can launch with a specific command line switch (for example, `java -jar app.jar --name="Spring"`). For one-off testing, you can launch with a specific command line switch (for example, `java -jar app.jar --name="Spring"`).
NOTE: The `env` and `configprops` endpoints can also be useful in determining why a property has a particular value.
You can use these two endpoints to diagnose unexpected property values.
Spring Boot also supports wildcard locations when loading configuration files. Spring Boot also supports wildcard locations when loading configuration files.
By default, a wildcard location of `config/*/` outside of your jar is supported. By default, a wildcard location of `config/*/` outside of your jar is supported.
Wildcard locations are also supported when specifying `spring.config.additional-location` and `spring.config.location`. Wildcard locations are also supported when specifying `spring.config.additional-location` and `spring.config.location`.

Loading…
Cancel
Save