anchor.diff:  
   ### <a id='user-uups'></a> Update a Service Instance ###
   
  -Use [cf update-user-provided-service](http://cli.cloudfoundry.org/en-US/cf/update-user-provided-service.html) (alias `cf uups`) to update one or more of the parameters for an existing user-provided service instance. 
  -The `cf uups` command uses the same syntax as `cf cups` [above](#user-cups) to set parameter values. The `cf uups` command does not update any parameter values that you do not supply.
  +To update one or more of the parameters for an existing user-provided service instance, use `cf update-user-provided-service` or `cf uups`. 
  +
  +For more information, see [update-user-provided-service](http://cli.cloudfoundry.org/en-US/cf/update-user-provided-service.html) in the _Cloud Foundry CLI Reference Guide_.
  +
  +The `cf uups` command does not update any parameter values that you do not supply.
   
   ## <a id='return-codes'></a> Retrieve cf CLI Return Codes
   
  
positive.code: 
  ## <a id='push'></a> Push an App
  
  By default, `cf push` recursively pushes the contents of the current working directory. Alternatively, you can provide a path using either a manifest or a command line option.
  
  - If the path is to a directory, `cf push` recursively pushes the contents of that directory instead of the current working directory.
  - If the path is to a file, `cf push` pushes only that file.
  
  <p class="note"><strong>Note</strong>: If you want to push more than a single file, but not the entire contents of a directory, consider using a <code>.cfignore</code> file to tell <code>cf push</code> what to exclude.</p>
  
  The `cf push` command pushes a new app or syncs changes to an existing app. See [push](http://cli.cloudfoundry.org/en-US/cf/push.html).
  
  ### <a id='push-procedure'></a> Push a New App or Push Changes to an App
  
  `cf push` requires an app name, which you provide either in a manifest
  or at the command line.
  
  `cf push` locates the `manifest.yml` in the current working
  directory by default, or in the path provided by the `-f` option.
  
  To push an app:
  
  1. Log in to the cf CLI:
      
  
negative.code:     ```
      Where `APP-NAME` is the name of the app. 
  
  
  ### <a id='push-path'></a> Push an App Using a Manifest 
  
  You can provide a path to a manifest file when you push an app. The manifest file may include information such as the name of the app, disk limit, and number of instances. You can use a manifest file rather than adding flags to the `cf push` command. 
  
  `cf push` locates the `manifest.yml` file in the current working
  directory by default. Or, you can provide a path to the manifest with the `-f` flag.
  
  For more information, see [push](http://cli.cloudfoundry.org/en-US/cf/push.html) in the _Cloud Foundry CLI Reference Guide_. 
  
  <p class="note"><strong>Note</strong>: When you provide an app name at the command line, <code>cf push</code> uses that app name whether or not there is a different app name in the manifest. If the manifest describes multiple apps, you can push a single app by providing its name at the command line; the cf CLI does not push the others. Use these behaviors for testing.</p> 
  
  
  ### <a id='push-buildpack'></a> Push an App with a Buildpack
  
  You can specify a buildpack when you push an app with the `-b` flag. If you use the `-b` flag to specify a buildpack, the app remains permanently linked to that buildpack. To use the app with a different buildpack, you must delete the app and then push it again.
  
  For more information about available buildpacks, see [Buildpacks](https://docs.cloudfoundry.org/buildpacks/).
  
  The following example pushes an app called `my-awesome-app` to the URL `http://my-awesome-app.example.com` and specifies the Ruby buildpack with the `-b` flag:
  
  