anchor.diff:  [[production-ready-cloudfoundry-custom-security]]
   === Custom Security Configuration
   If you define custom security configuration and you want extended Cloud Foundry actuator
  -support, you should ensure that `/cloudfoundryapplication/**` paths are open. Without
  -a direct open route, your Cloud Foundry application manager is not able to obtain
  -endpoint data.
  +support, you should ensure that `/cloudfoundryapplication/**` paths are open. Without a
  +direct open route, your Cloud Foundry application manager is not able to obtain endpoint
  +data.
   
   For Spring Security, you typically include something like
   `mvcMatchers("/cloudfoundryapplication/**").permitAll()` in your configuration, as shown
  
positive.code: |Lets the application be gracefully shutdown (not enabled by default).
  
  |`status`
  |Shows application status information (that is, `health` status with no additional details).
  
  |`threaddump`
  |Performs a thread dump.
  
negative.code: 
  [[production-ready-application-info-build]]
  ==== Build Information
  If a `BuildProperties` bean is available, the `info` endpoint can also publish information
  about your build. This happens if a `META-INF/build-info.properties` file is available in
  the classpath.
  
  TIP: The Maven and Gradle plugins can both generate that file. See
  "<<howto.adoc#howto-build-info,Generate build information>>" for more details.
  