anchor.diff:  [source,bash,options="nowrap"]
   ----
   skipper:>install --release-name helloworldpcf --package-name helloworld --package-version 1.0.0 --platform-name cf-dev --properties spec.deploymentProperties.spring.cloud.deployer.cloudfoundry.route=helloworldpcf.cfapps.io
  -Released helloworld-pcf. Now at version v1.
  +Released helloworldpcf. Now at version v1.
   ----
   
   If you do not specify `--platform-name cf-dev` the command will fail since the command property defaults to a platform named `default`.  Instead of specifying it, you can register this Cloud Foundry Platform account in the manifest with the name `default` instead of `cf-dev`.
  
positive.code: ----
  
  A more typical upgrade process is not to change application properties, but to change the version of the application because the code has change.  We will now upgrade the release to use a new maven artifact, version 1.0.1, which also corresponds to version 1.0.1 of the helloworld skipper package.
  In this case we will not add any additional properties other than the route.
  
  [source,bash,options="nowrap"]
  ----
  
negative.code: [source,bash,options="nowrap"]
  ----
  skipper:>status --release-name helloworldpcf
  ╔═══════════════╤════════════════════════════════════════════════╗
  ║Last Deployed  │Tue Oct 24 22:54:30 EDT 2017                    ║
  ║Status         │DEPLOYED                                        ║
  ║Platform Status│The applications are being deployed.            ║
  ║               │[helloworldpcf-helloworld-v1], State = [partial]║
  ╚═══════════════╧════════════════════════════════════════════════╝
  ----
  
  Eventually the Platform Status will say `All applications have been successfully deployed.`
  