SpringCloud/spring-cloud-commons
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Sync docs from 2.2.x to gh-pages

Browse Source
This commit is contained in:
buildmaster
2020-04-30 13:35:37 +00:00
parent 91058c1942
commit 5bd938a737
3 changed files with 10 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
2.2.x/reference/html/appendix.html
View File

@@ -136,7 +136,7 @@ Also, you can define your own properties.
<tbody>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">spring.cloud.compatibility-verifier.compatible-boot-versions</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">2.1.x</p></td>
<td class="tableblock halign-left valign-top"></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Default accepted versions for the Spring Boot dependency. You can set {@code x} for the patch version if you don&#8217;t want to specify a concrete value. Example: {@code 3.4.x}</p></td>
</tr>
<tr>
@@ -315,6 +315,11 @@ Also, you can define your own properties.
<td class="tableblock halign-left valign-top"><p class="tableblock">Additional class names for beans to post process into refresh scope.</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">spring.cloud.refresh.never-refreshable</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">true</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Comma separated list of class names for beans to never be refreshed or rebound.</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">spring.cloud.service-registry.auto-registration.enabled</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">true</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Whether service auto-registration is enabled. Defaults to true.</p></td>

15
2.2.x/reference/html/index.html
View File

@@ -1623,22 +1623,11 @@ healthy instances after querying the external ServiceDiscovery.
</table>
</div>
<div class="paragraph">
<p>The <code>HealthCheckServiceInstanceListSupplier</code> uses <code>InstanceHealthChecker</code> to verify if the instances are
alive. We provide a default <code>PingHealthChecker</code> instance. It uses <code>WebClient</code> to execute
requests against the <code>health</code> endpoint of the instance. You can also provide your own implementation
of <code>InstanceHealthChecker</code> instead.</p>
</div>
<div class="paragraph">
<p><code>HealthCheckServiceInstanceListSupplier</code> uses properties prefixed with
<code>spring.cloud.loadbalancer.healthcheck</code>. You can set the <code>initialDelay</code> and <code>interval</code>
for the scheduler.</p>
</div>
<div class="paragraph">
<p>For the <code>PingHealthChecker</code>, 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 <code>spring.cloud.loadbalancer.healthcheck.path.default</code>. You can also set a specific value
for any given service by setting the value of the <code>spring.cloud.loadbalancer.healthcheck.path.[SERVICE_ID]</code>,
substituting the <code>[SERVICE_ID]</code> with the correct ID of your service. If the path is not set,
<code>/actuator/health</code> is used by default.</p>
for any given service by setting the value of the <code>spring.cloud.loadbalancer.healthcheck.path.[SERVICE_ID]</code>, substituting the <code>[SERVICE_ID]</code> with the correct ID of your service. If the path is not set, <code>/actuator/health</code> is used by default.</p>
</div>
<div class="paragraph">
<p>In order to use the health-check scheduler approach, you will have to instantiate a <code>HealthCheckServiceInstanceListSupplier</code> bean in a <a href="#custom-loadbalancer-configuration">custom configuration</a>.</p>

15
2.2.x/reference/html/spring-cloud-commons.html
View File

@@ -1623,22 +1623,11 @@ healthy instances after querying the external ServiceDiscovery.
</table>
</div>
<div class="paragraph">
<p>The <code>HealthCheckServiceInstanceListSupplier</code> uses <code>InstanceHealthChecker</code> to verify if the instances are
alive. We provide a default <code>PingHealthChecker</code> instance. It uses <code>WebClient</code> to execute
requests against the <code>health</code> endpoint of the instance. You can also provide your own implementation
of <code>InstanceHealthChecker</code> instead.</p>
</div>
<div class="paragraph">
<p><code>HealthCheckServiceInstanceListSupplier</code> uses properties prefixed with
<code>spring.cloud.loadbalancer.healthcheck</code>. You can set the <code>initialDelay</code> and <code>interval</code>
for the scheduler.</p>
</div>
<div class="paragraph">
<p>For the <code>PingHealthChecker</code>, 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 <code>spring.cloud.loadbalancer.healthcheck.path.default</code>. You can also set a specific value
for any given service by setting the value of the <code>spring.cloud.loadbalancer.healthcheck.path.[SERVICE_ID]</code>,
substituting the <code>[SERVICE_ID]</code> with the correct ID of your service. If the path is not set,
<code>/actuator/health</code> is used by default.</p>
for any given service by setting the value of the <code>spring.cloud.loadbalancer.healthcheck.path.[SERVICE_ID]</code>, substituting the <code>[SERVICE_ID]</code> with the correct ID of your service. If the path is not set, <code>/actuator/health</code> is used by default.</p>
</div>
<div class="paragraph">
<p>In order to use the health-check scheduler approach, you will have to instantiate a <code>HealthCheckServiceInstanceListSupplier</code> bean in a <a href="#custom-loadbalancer-configuration">custom configuration</a>.</p>