anchor.diff:  ---
   
   
  -This topic describes the major changes between the cf CLI v6 and cf CLI v7. 
  +This topic describes the major changes between the cf CLI v6 and cf7 beta CLI. 
   
   ## <a id="overview"></a> Overview
   
   
  -The cf CLI v7's, and the backing v3 CC API, main goal is to unlock new app developer workflows for users who require granular control of their apps and other, more advanced, deployment strategies; see [New Workflows Supported](#new-workflows) for more information. The v3 CC API unlocks developer workflows that were previously limited by the v2 CC API. 
  -In order to do so, the cf CLI v7 beta is under active development to convert commands to call the [Cloud Foundry API (CC API) v3](https://v3-apidocs.cloudfoundry.org/index.html#introduction) instead of the [CC API v2](http://apidocs.cloudfoundry.org/). 
  -
  -Since both the cf CLI v7 beta and the backing CC API v3 are both in active development, it is important to note that the cf CLI v7 beta is subject to change as we move toward completing development. However, we aim to provide:
  +The cf7 CLI's, and the backing v3 CC API, main goal is to unlock new app developer workflows for users who require granular control of their apps and other, more advanced, deployment strategies; see [New Workflows Supported](#new-workflows) for more information. The v3 CC API unlocks developer workflows that were previously limited by the v2 CC API. 
  +In order to do so, the cf7 CLI beta is under active development to convert commands to call the [Cloud Foundry API (CC API) v3](https://v3-apidocs.cloudfoundry.org/index.html#introduction) instead of the [CC API v2](http://apidocs.cloudfoundry.org/). 
  +
  +Since both the cf CLI v7 beta and the backing CC API v3 are both in active development, it is important to note that the cf7 CLI beta is subject to change as we move toward completing development. However, we aim to provide:
   - a seamless upgrade experience from the cf CLI v6. To do so, we've kept changes to a minimal, and where there are changes we've incorporated feedback from the Community to simplify the cf CLI user experience
   - where a change was made that might potentially cause a breaking change in a scripting environment, we've provided details below and alternative workflows where possible
   
   To understand the differences between specific commands, see [Command Differences](#differences). 
   
  -<p class="note"><strong>Note</strong>: Additionally, in order to complete the cf CLI v7 beta in a timely matter, we develop and test against the latest CAPI release candidate. </p>
  -
  -<p class="note"><strong>Note</strong>: Since the cf CLI v7 is in beta mode, not all cf CLI v7 commands are backed by the CC API v3. As a result, commands still fall back to the v2 API. As we release the cf CLI v7 beta, more v3 resources will be developed along with the cf CLI v7 support for it.</p>
  -
  -## <a id="new-workflows"></a> New Workflows Supported on the cf CLI v7
  -
  -cf CLI v7 uses CAPI v3, which offers developers more granular control over their apps. It enables new workflows by exposing packages, droplets, builds, and processes. CC API v3 also includes new resources such as sidecars, manifests, deployments.
  -
  -The following list provides an overview of key new features available through the cf CLI v7 beta: 
  +<p class="note"><strong>Note</strong>: Additionally, in order to complete the cf7 CLI beta in a timely matter, we develop and test against the latest CAPI release candidate. </p>
  +
  +<p class="note"><strong>Note</strong>: Since the cf7 CLI is in beta mode, not all cf7 CLI commands are backed by the CC API v3. As a result, commands still fall back to the v2 API. As we release the cf7 CLI beta, more v3 resources will be developed along with the cf7 CLI support for it.</p>
  +
  +## <a id="new-workflows"></a> New Workflows Supported on the cf7 CLI
  +
  +cf7 CLI uses CAPI v3, which offers developers more granular control over their apps. It enables new workflows by exposing packages, droplets, builds, and processes. CC API v3 also includes new resources such as sidecars, manifests, deployments.
  +
  +The following list provides an overview of key new features available through the cf7 CLI beta: 
   
   * [Rolling App Deployments (Beta)](https://docs.cloudfoundry.org/devguide/deploy-apps/rolling-deploy.html): Push updates to apps without incurring downtime.
   * [Running cf push Sub-Step Commands](https://docs.cloudfoundry.org/devguide/push-sub-commands.html): Exercise granular control over the cf push process. These commands break down the cf push process into sub-steps that can run independently.
  
positive.code: </td>
  </tr>
  <tr>
  <td style="vertical-align:top"><code>cf push</code></td>
  <td>
  <ul>
  	        <li><strong>[Removed flag]</strong>: <code>--routh-path</code> You can use the <code>routes</code> property in the manifest instead. </li>
  
negative.code: </td>
  </tr>
  <tr>
  <td><code>cf7 create-service-auth-token</code></td>
  <td><i>Removed command because the V1 Broker API was deprecated as of January 2015.</i> 
  </td>
  </tr>
  <tr>
  <td ><code>cf7 create-domain</code></td>
  <td><ul>
  		<li><strong>[Renamed]</strong>: This command is renamed to <code>cf create-private-domain</code>.</li>
  		<li><strong>[Update]</strong>: No longer supports router groups and TCP routing removed in favor of different functionality currently being explored by the Networking team.</li>
  