Rename AutoConfigurationReportEndpoint to ConditionsEndpoint

This commit further aligns the change to ConditionEvaluationReport by
renaming the 'autoconfig' endpoint to 'conditions'.

Closes gh-2945

spring-boot-project/spring-boot-docs/src/main/asciidoc/appendix-application-properties.adoc

@@ -1077,13 +1077,6 @@ content into your application; rather pick only the properties that you need.
 	endpoints.auditevents.web.enabled= # Expose the auditevents endpoint as a Web endpoint.
 	endpoints.auditevents.web.path=auditevents # Path of the auditevents endpoint.
 
-	# AUTO-CONFIGURATION REPORT ENDPOINT ({sc-spring-boot-actuator-autoconfigure}/condition/AutoConfigurationReportEndpoint.{sc-ext}[AutoConfigurationReportEndpoint])
-	endpoints.autoconfig.cache.time-to-live=0 # Maximum time in milliseconds that a response can be cached.
-	endpoints.autoconfig.enabled= # Enable the autoconfig endpoint.
-	endpoints.autoconfig.jmx.enabled= # Expose the autoconfig endpoint as a JMX MBean.
-	endpoints.autoconfig.web.enabled= # Expose the autoconfig endpoint as a Web endpoint.
-	endpoints.autoconfig.web.path=autoconfig # Path of the autoconfig endpoint.
-
 	# BEANS ENDPOINT ({sc-spring-boot-actuator}/beans/BeansEndpoint.{sc-ext}[BeansEndpoint])
 	endpoints.beans.cache.time-to-live=0 # Maximum time in milliseconds that a response can be cached.
 	endpoints.beans.enabled= # Enable the beans endpoint.
@@ -1091,6 +1084,13 @@ content into your application; rather pick only the properties that you need.
 	endpoints.beans.web.enabled= # Expose the beans endpoint as a Web endpoint.
 	endpoints.beans.web.path=beans # Path of the beans endpoint.
 
+	# CONDITIONS REPORT ENDPOINT ({sc-spring-boot-actuator-autoconfigure}/condition/ConditionsReportEndpoint.{sc-ext}[ConditionsReportEndpoint])
+	endpoints.conditions.cache.time-to-live=0 # Maximum time in milliseconds that a response can be cached.
+	endpoints.conditions.enabled= # Enable the conditions endpoint.
+	endpoints.conditions.jmx.enabled= # Expose the conditions endpoint as a JMX MBean.
+	endpoints.conditions.web.enabled= # Expose the conditions endpoint as a Web endpoint.
+	endpoints.conditions.web.path=conditions # Path of the conditions endpoint.
+
 	# CONFIGURATION PROPERTIES REPORT ENDPOINT ({sc-spring-boot-actuator}/context/properties/ConfigurationPropertiesReportEndpoint.{sc-ext}[ConfigurationPropertiesReportEndpoint])
 	endpoints.configprops.cache.time-to-live=0 # Maximum time in milliseconds that a response can be cached.
 	endpoints.configprops.enabled= # Enable the configprops endpoint.

spring-boot-project/spring-boot-docs/src/main/asciidoc/appendix-auto-configuration-classes.adoc

@@ -2,10 +2,10 @@
 [[auto-configuration-classes]]
 == Auto-configuration classes
 Here is a list of all auto-configuration classes provided by Spring Boot, with links to
-documentation and source code. Remember to also look at the autoconfig report in your
+documentation and source code. Remember to also look at the conditions report in your
 application for more details of which features are switched on.
 (To do so, start the app with `--debug` or `-Ddebug` or, in an Actuator application, use
-the `autoconfig` endpoint).
+the `conditions` endpoint).
 
 
 

spring-boot-project/spring-boot-docs/src/main/asciidoc/howto.adoc

@@ -54,7 +54,7 @@ sometimes things fail, and it can be hard to tell why.
 
 There is a really useful `ConditionEvaluationReport` available in any Spring Boot
 `ApplicationContext`. You can see it if you enable `DEBUG` logging output. If you use
-the `spring-boot-actuator`, there is also an `autoconfig` endpoint that renders the report
+the `spring-boot-actuator`, there is also a `conditions` endpoint that renders the report
 in JSON. Use that endpoint to debug the application and see what features have been added (and
 which not) by Spring Boot at runtime.
 
@@ -65,7 +65,7 @@ reading the code, remember the following rules of thumb:
   `+@Conditional*+` annotations to find out what features they enable and when. Add
   `--debug` to the command line or a System property `-Ddebug` to get a log on the
   console of all the auto-configuration decisions that were made in your app. In a running
-  Actuator app, look at the `autoconfig` endpoint (`/application/autoconfig` or the JMX
+  Actuator app, look at the `conditions` endpoint (`/application/conditions` or the JMX
   equivalent) for the same information.
 * Look for classes that are `@ConfigurationProperties` (such as
   {sc-spring-boot-autoconfigure}/web/ServerProperties.{sc-ext}[`ServerProperties`])

spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc

@@ -71,9 +71,9 @@ The following technology-agnostic endpoints are available:
 |`auditevents`
 |Exposes audit events information for the current application.
 
-|`autoconfig`
-|Displays an auto-configuration report showing all auto-configuration candidates and the
- reason why they '`were`' or '`were not`' applied.
+|`conditions`
+|Showing the conditions that were evaluated on configuration and auto-configuration
+ classes and the reasons why they did or did not match.
 
 |`beans`
 |Displays a complete list of all the Spring beans in your application.

spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc

@@ -3319,7 +3319,8 @@ The line in the preceding example passes a value of `true` for the
 
 By default, the DDL execution (or validation) is deferred until the `ApplicationContext`
 has started. There is also a `spring.jpa.generate-ddl` flag, but it is not used if
-Hibernate autoconfig is active, because the `ddl-auto` settings are more fine-grained.
+Hibernate auto-configuration is active, because the `ddl-auto` settings are more
+fine-grained.