anchor.diff:  cf env app | grep APPLICATION_DOMAIN || cf set-env app APPLICATION_DOMAIN ${DOMAIN}
   
   cf services | grep configserver && cf bind app configserver
  -    
  +
   cf restart app
   cf create-service-broker app user secure http://app.${DOMAIN}
   
  -for f in `cf curl /v2/service_plans | grep '\"guid' | sed -e 's/.*: "//' -e 's/".*//'`; do 
  +for f in `cf curl /v2/service_plans | grep '\"guid' | sed -e 's/.*: "//' -e 's/".*//'`; do
       cf curl v2/service_plans/$f -X PUT -d '{"public":true}'
   done
   
  
positive.code: https://github.com/Netflix/eureka[Eureka core] dependency, and you
  can expose it as a Eureka service, then any service which registers
  with Eureka will also become a Cloud Foundry service.
  
  
  
negative.code: * `cloudfoundry.service.definition.*` is bound to a
    `ServiceDefinition` (defined in spring-boot-cf-service-broker) which
    has optional setters for plans and metadata.
  
  * `cloudfoundry.service.broker.*` is bound to an internal bean. It has
    optional setters for "name" (the service name), "description" (user
    friendly description) and "prefix" (used to create a unique id from
    the name).
  
  An app which binds to your service will get credentials that contain a
  "uri" property linking to your service. A Spring Boot app can bind to
  that through the `vcap.services.[service].credentials.uri` environment
  