anchor.diff:  
   ### <a id='new-route'></a> Map a Route to an App
   
  -You can use the `--hostname` flag with the `cf push` command to provide a hostname for your app.
  -
  -If you do not provide a hostname, `cf push` routes your app to a URL of the form `APPNAME.DOMAIN`, where `APPNAME` is the name of your app and `DOMAIN` is your default domain. 
  -
  -For information about mapping a route to your app, see [Routes and Domains](https://docs.cloudfoundry.org/devguide/deploy-apps/routes-domains.html). 
  -
  +You can provide a hostname for your app when you push the app. If you do not provide a hostname, the `cf push` command routes your app to a URL of the form `APPNAME.DOMAIN`, where `APPNAME` is the name of your app and `DOMAIN` is your default domain. 
  +
  +For information about mapping a route to your app, see [Routes and Domains](https://docs.cloudfoundry.org/devguide/deploy-apps/routes-domains.html).
  +
  +To map a route to the app:
  +
  +1. Log in to the cf CLI:
  +
  +    ```
  +    cf login
  +    ```
  +
  +1. Map a route:
  +
  +    ```
  +    cf push APP-NAME --hostname MY-HOSTNAME
  +    ```
  +    Where:
  +      * `APP-NAME` is the name of the app.
  +      * `MY-HOSTNAME` is the hostname.
   
   ## <a id='user-provided'></a> Manage User-Provided Service Instances
   
  
positive.code: 
  ## <a id='login'></a> Log In With the API
  
  You can write a script to log in and set your target using the non-interactive cf api , cf auth, and [cf target](http://cli.cloudfoundry.org/en-US/cf/target.html) commands.
  
  [cf api](http://cli.cloudfoundry.org/en-US/cf/api.html)
  [cf auth](http://cli.cloudfoundry.org/en-US/cf/auth.html)
  
  After you log in, the cf CLI saves a `config.json` file that contains your API endpoint, org, space values, and access token.
  
  
negative.code: 
  #### <a id='interactive'></a> Supply Parameters Interactively
  
  This procedure describes how to create a new service instance by supplying parameters interactively:
  
  To supply parameters interactively:
  
  1. Log in to the cf CLI:
  
      ```
      cf login
      ```
  
  1. List parameters in a comma-separated list after the `-p` flag:
  
      ```
      cf cups MY-SERVICE -p "MY-PARAMETER, MY-SECOND-PARAMETER, MY-THIRD-PARAMETER"
      ```
      Where:
      * `MY-SERVICE` is the name of the service to create.
      * `MY-PARAMETER`, `MY-SECOND-PARAMETER`, and `MY-THIRD-PARAMETER` are parameters such as username, password, host, port, and database name.
  
      For example:  
  
      <pre class="terminal">$ cf cups sql-service-instance -p "host, port, dbname, username, password"
      host> mysql.example.com
      port> 1433
      dbname> mysqldb
      username> admin
      password> Pa55w0rd
      Creating user provided service sql-service-instance in org example-org / space development as username@example.com...
      OK
      </pre>
  
  #### <a id='non-interactive'></a> Supply Parameters Non-Interactively
  
  This procedure describes how to create a new service instance by supplying parameters non-interactively:
  
  To supply parameters non-interactively:
  
  1. Log in to the cf CLI:
  
      ```
      cf login
      ```
  
  1. Pass parameters and their values in as a JSON hash, bound by single quotes, after the `-p` tag.
  
      ```
      cf cups MY-SERVICE -p '{"host":"HOSTNAME", "port":"PORT"}'
      ``` 
      Where:
      * `MY-SERVICE` is the name of the service to create. 
      * `HOSTNAME` and `PORT` are service parameters.
  
      For example: 
      <pre class="terminal">$ cf cups sql-service-instance -p '{"host":"mysql.example.com", "port":"1433", "dbname":"mysqldb", "username":"admin","password":"pa55woRD"}'
      Creating user provided service sql-service-instance in org example-org / space development as username<span>@</span>example.com...
      OK
      </pre>
  
  
  #### <a id='third-party'></a> Supply Parameters Through a Third-Party
  
  For specific log service instructions, see [Service-Specific Instructions for Streaming Application Logs](https://docs.cloudfoundry.org/devguide/services/log-management-thirdparty-svc.html).
  
  To create a service instance that sends data to a third-party:
  
  1. Log in to the cf CLI:
  
      ```
      cf login
      ```
  1. Create a service instance that sends data to a third-party:
  
      ```
      cf cups MY-SERVICE -l THIRD-PARTY-DESTINATION-URL
      ```
      Where:
      * `MY-SERVICE` is the name of the service to create.
      * `THIRD-PARTY-DESTINATION-URL` is the external URL of the third-party service.
  
      For example, the following command creates a service instance that sends log information to the syslog drain URL of a third-party log management service: 
  
      <pre class="terminal">$ cf cups mylog -l syslog://logs4.example.com:25258
      Creating user provided service mylog in org example-org / space development as username<span>@</span>example.com...
      OK
      </pre>
  
  ### <a id='bind-unbind'></a> Bind and Unbind Service Instances
  
  