anchor.diff:              "env": [
                 {
                   "name": "MYSQL_USER",
  -                "value": "${MYSQL_USER}"
  +                "value": "${MYSQL_USER}" <2>
                 },
                 {
                   "name": "MYSQL_PASSWORD",
  -                "value": "${MYSQL_PASSWORD}"
  +                "value": "${MYSQL_PASSWORD}" <3>
                 },
                 {
                   "name": "MYSQL_DATABASE",
  -                "value": "${MYSQL_DATABASE}"
  +                "value": "${MYSQL_DATABASE}" <4>
                 }
               ]
             }
  
positive.code: ----
  
  <1> Other fields on the `DeploymentConfig` are omitted
  
  ====
  
  === External Database Environment Variables
  
  Using an external service in your application is just like using an internal service. Your
  application will be injected with environment variables for the service and the additional
  environment variables with the credentials described above. In our example, The 'helloworld'
  container will receive the following environment variables:
  
  * `EXTERNAL_MYSQL_SERVICE_SERVICE_HOST`=[replaceable]#<IP_Address>#
  * `EXTERNAL_MYSQL_SERVICE_SERVICE_PORT`=[replaceable]#<Port_Number>#
  
negative.code: 
  === Creating the Service
  
  The first step in integrating with an external service is to create an OpenShift
  service to represent it. This is similar to creating an internal service; the
  difference is in the service's `Selector` field.
  
  Internal OpenShift services use the `Selector` field to associate pods with
  services via labels. A system component called `EndpointsController`
  synchronizes the endpoints for services that specify selectors with the pods
  that match the selector. The service proxy and OpenShift router load-balance
  requests to the service amongst the service's endpoints.
  
  The only difference between an internal OpenShift service and a service that
  represents an external resource is that no pods need to be associated with an
  external service. To represent external services, leave the `Selector` field
  unset. This makes the `EndpointsController` ignore the service and allows you to
  specify endpoints manually:
  
  ====
  
  