anchor.diff:          profileSeparator: '::'
   ----
   
  +CAUTION: If you have set `spring.cloud.bootstrap.enabled=true` or `spring.config.use-legacy-processing=true`, or included `spring-cloud-starter-bootstrap`, then the above values will need to be placed in `bootstrap.yml` instead of `application.yml`.
  +
   * `enabled` setting this value to "false" disables Consul Config
   * `prefix` sets the base folder for configuration values
   * `defaultContext` sets the folder name used by all applications
  
positive.code: 
  To get started with Consul Configuration use the starter with group `org.springframework.cloud` and artifact id `spring-cloud-starter-consul-config`. See the https://projects.spring.io/spring-cloud/[Spring Cloud Project page] for details on setting up your build system with the current Spring Cloud Release Train.
  
  This will enable auto-configuration that will setup Spring Cloud Consul Config.
  
  === Customizing
  
  Consul Config may be customized using the following properties:
  
  .bootstrap.yml
  ----
  spring:
    cloud:
  
negative.code: [[spring-cloud-consul-failfast]]
  === Fail Fast
  
  It may be convenient in certain circumstances (like local development or certain test scenarios) to not fail if consul isn't available for configuration. Setting `spring.cloud.consul.config.fail-fast=false` will cause the configuration module to log a warning rather than throw an exception. This will allow the application to continue startup normally.
  
  CAUTION: If you have set `spring.cloud.bootstrap.enabled=true` or `spring.config.use-legacy-processing=true`, or included `spring-cloud-starter-bootstrap`, then the above values will need to be placed in `bootstrap.yml` instead of `application.yml`.
  
  [[spring-cloud-consul-retry]]
  == Consul Retry
  