From 265243b59d07e4d0872fbdf0de79a43dc4eaec2e Mon Sep 17 00:00:00 2001 From: Olga Maciaszek-Sharma Date: Thu, 20 Oct 2022 16:20:16 +0200 Subject: [PATCH] Fix after review. --- docs/src/main/asciidoc/spring-cloud-config.adoc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/src/main/asciidoc/spring-cloud-config.adoc b/docs/src/main/asciidoc/spring-cloud-config.adoc index 7c8e6204..87083757 100644 --- a/docs/src/main/asciidoc/spring-cloud-config.adoc +++ b/docs/src/main/asciidoc/spring-cloud-config.adoc @@ -1698,7 +1698,7 @@ NOTE: The `RefreshRemoteApplicationEvent` is transmitted only if the `spring-clo NOTE: The default configuration also detects filesystem changes in local git repositories. In that case, the webhook is not used. However, as soon as you edit a config file, a refresh is broadcast. -=== AOT and native image support +=== AOT and Native Image Support Since `4.0.0`, Spring Cloud Config Server supports Spring AOT transformations. However, for the time being, GraalVM native images are not supported. Implementing native image support is blocked by https://github.com/oracle/graal/issues/5134[graal#5134] and will likely require the completion of the work on https://github.com/graalvm/taming-build-time-initialization[https://github.com/graalvm/taming-build-time-initialization] to be fixed. @@ -1975,14 +1975,14 @@ String name = "World"; The preceding code would sets the value of the `name` variable to `appAsecret`. -=== AOT and native image support +=== AOT and Native Image Support Since `4.0.0`, Spring Cloud Config Client supports Spring AOT transformations and GraalVM native images. WARNING: AOT and native image support is not available for <> (with `spring.config.use-legacy-processing=true`). -WARNING: Refresh scope is not supported with native images. If you're going to run your config client application as a native image, make sure to set `spring.cloud.refresh.enabled` property to `false`. +WARNING: Refresh scope is not supported with native images. If you are going to run your config client application as a native image, make sure to set `spring.cloud.refresh.enabled` property to `false`. -WARNING: While building a project that contains Spring Cloud Config Client, it is necessary to make sure that the configuration data source that it connects to (such as, Spring Cloud Config Server, Consul, Zookeeper, Vault, etc.) is available. For example, if you retrieve configuration data from Spring Cloud Config Server, make sure you have its instance running and available at the port indicated in the Config Client setup. This is necessary because the application context is being optimized at build time and requires the target environment to be resolved. +WARNING: While building a project that contains Spring Cloud Config Client, you must make sure that the configuration data source that it connects to (such as, Spring Cloud Config Server, Consul, Zookeeper, Vault, and others) is available. For example, if you retrieve configuration data from Spring Cloud Config Server, make sure you have its instance running and available at the port indicated in the Config Client setup. This is necessary because the application context is being optimized at build time and requires the target environment to be resolved. WARNING: Since in AOT and native mode, configuration is being processed and the context is being optimised at build time, any properties that would influence bean creation (such as the ones used within bootstrap context) should be set to the same values at build time and runtime to avoid unexpected behaviour.