anchor.diff:  This is useful when applying configuration updates that require a restart, such as environment variables or service bindings. 
   
   * **cf CLI v7**:
  -
  -	```
  -	cf restart APP-NAME
  -	```
  +	* As of the cf CLI v7 beta, there is no way to restart with a rolling deploy strategy. 
   * **cf CLI v6**:
   
   	```
  
positive.code: 	</tr>
  	<tr>
  		<td>App Manifests</td>
  		<td>The <code>v3-zdt-push</code> command does not support providing an app manifest with the <code>-f</code> flag. If you have a `manifest.yml` file in your app directory, it is ignored. The cf CLI V7 beta does not have this limitation.</td>
  	</tr>
  	<tr>
  		<td>SSH to app instances</td>
  		<td>Pushing updates to your app with a <code>v3-zdt</code> command causes the new web
  			process and app GUID to mismatch. <code>cf ssh</code> does not handle this
  			scenario. You must use the <code>cf v3-ssh</code> command instead.</td>
  	</tr>
  	<tr>
  		<td>Multiple app versions</td>
  
negative.code: 
  ## <a id="prerequisites"></a>  Prerequisites
  
  The procedures in this topic require the following
  
  * **cf CLI v7**: 
  	* You must have the cf CLI v7. 
  	* You must have CAPI version [PLACEHOLDER]
  * **cf CLI v6**: 
  	* You must have cf CLI v6.40 or later. 
  	* The rolling deployment feature must be enabled for your installation.
  		* <%= vars.zdt_enable %>
  
  
  
  ## <a id="commands"></a> Commands
  
  