anchor.diff:  ----
   
   The preceding code would sets the value of the `name` variable to `appAsecret`.
  +
  +===  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 <<config-first-bootstrap, config first bootstrap>> (with `spring.config.use-legacy-processing=true`).
  +
  +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, 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.
  
positive.code: In that case, if you provide the `encrypt.*` configuration to locate a key, you can still have `/encrypt` and `/decrypt` endpoints, but you need to explicitly switch off the decryption of outgoing properties by placing `spring.cloud.config.server.encrypt.enabled=false` in `bootstrap.[yml|properties]`.
  If you do not care about the endpoints, it should work if you do not configure either the key or the enabled flag.
  
  == Serving Alternative Formats
  
  The default JSON format from the environment endpoints is perfect for consumption by Spring applications, because it maps directly onto the `Environment` abstraction.
  If you prefer, you can consume the same data as YAML or Java properties by adding a suffix (".yml", ".yaml" or ".properties") to the resource path.
  
negative.code: ====
  
  [[spring-cloud-config-serving-plain-text-aws-s3]]
  ==== AWS S3
  
  To enable serving plain text for AWS s3, the Config Server application needs to include a dependency on Spring Cloud AWS.
  For details on how to set up that dependency, see the
  