anchor.diff:  
   <strong><%= modified_date %></strong>
   
  -This topic covers how to configure and get started with the cf CLI. This page assumes you have the latest version of the cf CLI. See the [Installing the cf Command Line Interface](./install-go-cli.html) topic for installation instructions.
  +This topic covers how to configure and get started with the cf CLI. This page assumes you have the latest version of the cf CLI. 
  +See the [Installing the cf Command Line Interface](./install-go-cli.html) topic for installation instructions.
   
   ##<a id='i18n'></a>Localize ##
   
  
positive.code: 
  ## <a id='user-provided'></a> User-Provided Service Instances ##
  
  The cf CLI has three ways of creating and updating user-provided service instances: interactively, non-interactively, and in conjunction with third-party log management software as described in [RFC 6587](http://tools.ietf.org/html/rfc6587). When used with third-party logging, the cf CLI sends data formatted according to [RFC 5424](http://tools.ietf.org/html/rfc5424).
  
  Once created, user-provided service instances can be bound to an app with `cf bind-service`, unbound with `cf unbind-service`, renamed with `cf rename-service`, and deleted with `cf delete-service`.
  
  ### <a id='user-cups'></a>The cf create-user-provided-service Command ###
  
  The alias for `create-user-provided-service` is `cups`.
  
  To create a service instance in interactive mode, use the `-p` option with a comma-separated list of parameter names.
  The cf CLI then prompts you for each parameter in turn.
  
    <pre class="terminal">cf cups SERVICE_INSTANCE -p host, port, dbname, username, password</pre>
  
  To create a service instance non-interactively, use the `-p` option with a JSON hash of parameter keys and values.
  
    <pre class="terminal">cf cups SERVICE_INSTANCE -p '{"username":"admin","password":"pa55woRD"}'</pre>
  
  To create a service instance that drains information to third-party log management software, use the `-l SYSLOG_DRAIN_URL` option.
  
    <pre class="terminal">cf cups SERVICE_INSTANCE -l syslog://example.com:514</pre>
  
  ### <a id='user-uups'></a> The cf update-user-provided-service Command ###
  
  The alias for `update-user-provided-service` is `uups`.
  Use `cf update-user-provided-service` to update one or more of the attributes for a user-provided service instance.
  Attributes that you do not supply are not updated.
  
  To update a service instance non-interactively, use the `-p` option with a JSON hash of parameter keys and values.
  
    <pre class="terminal">cf uups SERVICE_INSTANCE -p '{"username":"USERNAME","password":"PASSWORD"}'</pre>
  
  To update a service instance that drains information to third-party log management software, use the `-l SYSLOG_DRAIN_URL` option.
  
    <pre class="terminal">cf uups SERVICE_INSTANCE -l syslog://example.com:514</pre>
  
  
  ## <a id='return-codes'></a> cf CLI Return Codes ##
  
  The cf CLI uses exit codes, which is helpful for scripting and for confirming that a command has run successfully. For example, run `echo $?` in the terminal. If the return code is `0`, the command was successful.
  
  ## <a id='help'></a> The cf help Command ##
  
  
negative.code: 
  Alternatively, you can write a script to log in and set your target using the non-interactive [cf api](./cf-help.html#getting-started), [cf auth](./cf-help.html#getting-started), and [cf target](./cf-help.html#getting-started) commands.
  
  Upon successful login, the cf CLI saves a `config.json` file containing your API endpoint, org, space values, and access token. 
  If you change these settings, the `config.json` file is updated accordingly.
  
  By default, `config.json` is located in your `~/.cf` directory. The `CF_HOME` environment variable allows you to locate the `config.json` file wherever you like.
  
  