anchor.diff:  resource pool for a BOSH deployment with errands must include one additional VM
   per errand.
   
  -To run an errand, use `bosh run errand ERRAND-NAME`. ERRAND-NAME must be an
  -errand job name provided in the deployment manifest.
  +Use `bosh run errand ERRAND-NAME` to run an errand. ERRAND-NAME must be the name of an errand provided in the deployment manifest.
   
   Example:
   
  
positive.code: The `bosh cancel errand` command terminates the errand process, releases the
  deployment lock, and returns the errand VM to the resource pool.
  
  ## <a id="logging"></a>Logging ##
  
  
  ### <a id="job-logging"></a>Logging ###
  
  ### <a id="errand-logging"></a>Logging ###
  
  ## <a id="errand-running"></a>Warnings and Additional Information ##
  
  * Errands do not have a notion of persistence. Persistent disk migration for errands is not supported.
  * Whenever an errand runs, BOSH initiates a deployment lock. This lock prevent all other deploys. Additionally, the BOSH CLI `cloudcheck` command is unavailable, and the health monitor does not scan and fix current deployments during the duration of the errand.
  * Currently, BOSH limits errand output to 1 MB. BOSH discards errand output greater than 1 MB.
negative.code: 1. Provisions and configures the VM for the errand
  1. Installs the errand code and all required packages and templates
  1. Runs the processes specified by the errand
  1. Sends all output of the errand to the BOSH CLI for output
  1. Releases the deployment lock
  1. Release the VM back into the resource pool
  
  