diff --git a/2.2.x/reference/html/appendix.html b/2.2.x/reference/html/appendix.html index 7dccf073..f0e502af 100644 --- a/2.2.x/reference/html/appendix.html +++ b/2.2.x/reference/html/appendix.html @@ -136,7 +136,7 @@ Also, you can define your own properties.

spring.cloud.compatibility-verifier.compatible-boot-versions

-

2.1.x

+

Default accepted versions for the Spring Boot dependency. You can set {@code x} for the patch version if you don’t want to specify a concrete value. Example: {@code 3.4.x}

@@ -315,6 +315,11 @@ Also, you can define your own properties.

Additional class names for beans to post process into refresh scope.

+

spring.cloud.refresh.never-refreshable

+

true

+

Comma separated list of class names for beans to never be refreshed or rebound.

+ +

spring.cloud.service-registry.auto-registration.enabled

true

Whether service auto-registration is enabled. Defaults to true.

diff --git a/2.2.x/reference/html/index.html b/2.2.x/reference/html/index.html index 6855d300..2047e623 100644 --- a/2.2.x/reference/html/index.html +++ b/2.2.x/reference/html/index.html @@ -1623,22 +1623,11 @@ healthy instances after querying the external ServiceDiscovery.
-

The HealthCheckServiceInstanceListSupplier uses InstanceHealthChecker to verify if the instances are -alive. We provide a default PingHealthChecker instance. It uses WebClient to execute -requests against the health endpoint of the instance. You can also provide your own implementation -of InstanceHealthChecker instead.

-
-

HealthCheckServiceInstanceListSupplier uses properties prefixed with spring.cloud.loadbalancer.healthcheck. You can set the initialDelay and interval -for the scheduler.

-
-
-

For the PingHealthChecker, you can set the default path for the healthcheck URL by setting +for the scheduler. You can set the default path for the healthcheck URL by setting the value of the spring.cloud.loadbalancer.healthcheck.path.default. You can also set a specific value -for any given service by setting the value of the spring.cloud.loadbalancer.healthcheck.path.[SERVICE_ID], -substituting the [SERVICE_ID] with the correct ID of your service. If the path is not set, -/actuator/health is used by default.

+for any given service by setting the value of the spring.cloud.loadbalancer.healthcheck.path.[SERVICE_ID], substituting the [SERVICE_ID] with the correct ID of your service. If the path is not set, /actuator/health is used by default.

In order to use the health-check scheduler approach, you will have to instantiate a HealthCheckServiceInstanceListSupplier bean in a custom configuration.

diff --git a/2.2.x/reference/html/spring-cloud-commons.html b/2.2.x/reference/html/spring-cloud-commons.html index 6855d300..2047e623 100644 --- a/2.2.x/reference/html/spring-cloud-commons.html +++ b/2.2.x/reference/html/spring-cloud-commons.html @@ -1623,22 +1623,11 @@ healthy instances after querying the external ServiceDiscovery.
-

The HealthCheckServiceInstanceListSupplier uses InstanceHealthChecker to verify if the instances are -alive. We provide a default PingHealthChecker instance. It uses WebClient to execute -requests against the health endpoint of the instance. You can also provide your own implementation -of InstanceHealthChecker instead.

-
-

HealthCheckServiceInstanceListSupplier uses properties prefixed with spring.cloud.loadbalancer.healthcheck. You can set the initialDelay and interval -for the scheduler.

-
-
-

For the PingHealthChecker, you can set the default path for the healthcheck URL by setting +for the scheduler. You can set the default path for the healthcheck URL by setting the value of the spring.cloud.loadbalancer.healthcheck.path.default. You can also set a specific value -for any given service by setting the value of the spring.cloud.loadbalancer.healthcheck.path.[SERVICE_ID], -substituting the [SERVICE_ID] with the correct ID of your service. If the path is not set, -/actuator/health is used by default.

+for any given service by setting the value of the spring.cloud.loadbalancer.healthcheck.path.[SERVICE_ID], substituting the [SERVICE_ID] with the correct ID of your service. If the path is not set, /actuator/health is used by default.

In order to use the health-check scheduler approach, you will have to instantiate a HealthCheckServiceInstanceListSupplier bean in a custom configuration.