anchor.diff:  ----
   
   <1> Other fields on the `DeploymentConfig` are omitted
  +<2> The username to use with the service.
  +<3> The passphrase to use with the service.
  +<4> The database name.
   
   ====
   
   === 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:
  +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
  +in the previous step. For example, a MySQL container receives the following
  +environment variables:
   
   * `EXTERNAL_MYSQL_SERVICE_SERVICE_HOST`=[replaceable]#<IP_Address>#
   * `EXTERNAL_MYSQL_SERVICE_SERVICE_PORT`=[replaceable]#<Port_Number>#
  
positive.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 there are no pods to associate an external service with. To represent external
  services, we just need to leave the `Selector` field unset. This will make the `EndpointsController`
  ignore the service and allow you to specify endpoints manually:
  
  ====
  
  
negative.code: * `MYSQL_PASSPHRASE`=[replaceable]#<MySQL_passphrase>#
  * `MYSQL_DATABASE_NAME`=[replaceable]#<MySQL_database>#
  
  The application is responsible for reading the coordinates and credentials for
  the service from the environment and establishing a connection with the database
  via the service.
  
  
  == External SaaS Provider
  