anchor.diff:  instances: 1
   services:
    singular-mysql:
  -  label: cleardb
  -  provider: cleardb
  +  label: mysql
  +  provider: mysql
     version: n/a
     plan: dev-sandbox
   
  
positive.code: 
  You can deploy multiple applications with one `cf push` command by describing them in a single manifest. In doing so, you need to pay extra attention to directory structure and path lines in the manifest.
  
  Suppose you want to deploy two applications, `spark` and `flame`, and you want `cf` to create and start `spark` before `flame`. You accomplish this by listing `spark` first in the manifest.
  
  In this situation there are two sets of bits you want to push. Let’s say that they are `spark.rb` in the `spark` directory and `flame.rb` in the `flame` directory. One level up, the `fireplace` directory contains the `spark` and the `flame` directories along with the `manifest.yml` file. Your plan is to run `cf` from `fireplace`, where you know it can find the manifest.
  
  Now that you have changed the directory structure and manifest location, the standard path line of `path: . ` no longer works. How can you ensure that `cf` finds the bits you want to push?
  
  
negative.code: cf unset-env <app> <name>
  ~~~
  
  Environment variables interact with manifests by somewhat complicated rules:
  
  * When you deploy an application for the first time, `cf` reads the variables described in the environment block of the manifest, and adds them to the environment of the container where the application is deployed.
  
  