A number of classes have been deprecated to implement the new health indicator groups feature. If you are configuring a custom HealthIndicator via CompositeHealthIndicatorConfiguration, you’ll need to update it to use CompositeHealthContributorConfiguration instead.

It is now possible to organize health indicators into groups. A typical example if you deploy your application to Kubernetes, you may want one different sets of health indicators for your “liveness” and “readiness” probes.

Groups can be configured via configuration properties. The following create a custom group with only the DataSource indicator:

The custom group can be invoked by hitting localhost:8080/actuator/health/custom.

Check the updated reference documentation for more details.

Flyway will be auto-configured to use any JavaMigration beans that are found in the application context.

The sanitization performed by the configprops and env endpoints has been improved to include URI properties. Any password found in the URI’s user information will now be sanitized.

Spring Boot 2.2.0.M6 moves to new versions of several Spring projects:

• Spring Framework 5.2.0.RC2

• Reactor Dysprosium-RC1

• Spring AMQP 2.2.0.RC1

• Spring Data Moore-RC3

• Spring Integration 5.2.0.RC1

• Spring Kafka 2.3.0.RC1

• Spring Security 5.2.0.RC1

• Spring Session Corn-M4

Numerous third-party dependencies have also been updated, some of the more noteworthy of which are the following:

• Flyway 6.0.1

• Kotlin 1.3.50

• Git commit id plugin 3.0.1

In addition to the changes listed above, there have also been lots of minor tweaks and improvements including:

• Configurable timeout for JMS listener container’s receive

• Support for Spring Session’s flush mode

• Support for Spring AMQP’s confirm-type

• Application properties for configuring Jetty’s thread pool

• Support for parallel test execution when using @AutoConfigureMockMvc with JUnit 5