From 6ced1d7f4e8caff773ef1dfba1cf8b22de2253d4 Mon Sep 17 00:00:00 2001 From: Wesley Ugang <35684516+wesuga@users.noreply.github.com> Date: Sat, 5 Dec 2020 01:27:17 +0800 Subject: [PATCH 1/2] 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 --- .../src/docs/asciidoc/spring-boot-features.adoc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/spring-boot-project/spring-boot-docs/src/docs/asciidoc/spring-boot-features.adoc b/spring-boot-project/spring-boot-docs/src/docs/asciidoc/spring-boot-features.adoc index 60f05a8f6521..300e480238ab 100644 --- a/spring-boot-project/spring-boot-docs/src/docs/asciidoc/spring-boot-features.adoc +++ b/spring-boot-project/spring-boot-docs/src/docs/asciidoc/spring-boot-features.adoc @@ -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`. 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. 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`. From 60bb33f231062a6f3cacb665cbc485e744632b48 Mon Sep 17 00:00:00 2001 From: Phillip Webb Date: Thu, 28 Jan 2021 15:46:28 -0800 Subject: [PATCH 2/2] Polish 'Add a tip about actuator endpoints' See gh-24336 --- .../src/docs/asciidoc/spring-boot-features.adoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/spring-boot-project/spring-boot-docs/src/docs/asciidoc/spring-boot-features.adoc b/spring-boot-project/spring-boot-docs/src/docs/asciidoc/spring-boot-features.adoc index 300e480238ab..7bf96c99eedb 100644 --- a/spring-boot-project/spring-boot-docs/src/docs/asciidoc/spring-boot-features.adoc +++ b/spring-boot-project/spring-boot-docs/src/docs/asciidoc/spring-boot-features.adoc @@ -496,8 +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`. 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. +TIP: The `env` and `configprops` endpoints can be useful in determining why a property has a particular value. You can use these two endpoints to diagnose unexpected property values. +See the "<>" section for details. Spring Boot also supports wildcard locations when loading configuration files. By default, a wildcard location of `config/*/` outside of your jar is supported.