anchor.diff:  	management.security.enabled=false
   ----
   
  -NOTE: By default, actuator endpoints are exposed on the same port that serves regular
  +CAUTION: By default, actuator endpoints are exposed on the same port that serves regular
   HTTP traffic. Take care not to accidentally expose sensitive information if you change
   the `management.security.enabled` property.
   
  -If you're deploying applications publicly, you may want to add '`Spring Security`' to
  -handle user authentication. When '`Spring Security`' is added, by default '`basic`'
  -authentication will be used with the username `user` and a generated password (which is
  -printed on the console when the application starts).
  -
  -TIP: Generated passwords are logged as the application starts. Search for '`Using default
  -security password`'.
  +If you deploy applications publicly, you may want to add '`Spring Security`' to
  +handle user authentication. When '`Spring Security`' is added, by default, '`basic`'
  +authentication is used. The username is`user` and the password is a random generated
  +password (which is printed on the console when the application starts).
  +
  +TIP: Generated passwords are logged as the application starts. To find the password in
  +the console, search for '`Using default security password`'.
   
   You can use Spring properties to change the username and password and to change the
   security role(s) required to access the endpoints. For example, you might set the following
  -in your `application.properties`:
  +properties in your `application.properties`:
   
   [source,properties,indent=0]
   ----
  
positive.code: 	{"status":"DOWN"}
  ----
  
  Sample detailed HTTP response:
  
  [source,indent=0]
  ----
  
negative.code: ----
  
  NOTE: The identifier for a given `HealthIndicator` is the name of the bean without the
  `HealthIndicator` suffix, if it exists. In the preceding example, the health information
  is available in an entry named `my`.
  
  In addition to Spring Boot's predefined {sc-spring-boot-actuator}/health/Status.{sc-ext}[`Status`]
  types, it is also possible for `Health` to return a custom `Status` that represents a
  new system state. In such cases, a custom implementation of the
  {sc-spring-boot-actuator}/health/HealthAggregator.{sc-ext}[`HealthAggregator`]
  interface also needs to be provided, or the default implementation has to be configured
  by using the `management.health.status.order` configuration property.
  
  For example, assume a new `Status` with code `FATAL` is being used in one of your
  `HealthIndicator` implementations. To configure the severity order, add the following
  to your application properties:
  
  [source,properties,indent=0]
  