anchor.diff:  	```
   	cf v3-zdt-restart APP-NAME
   	```
  +
  +* **CAPI v3**:
  +
  +    ```bash
  +    cf curl /v3/deployments \
  +    -X POST \
  +    -H "Content-type: application/json" \
  +    -d '{
  +      "droplet": {
  +        "guid": "DROPLET-GUID"
  +      },
  +      "strategy": "rolling",
  +      "relationships": {
  +        "app": {
  +          "data": {
  +            "guid": "APP-GUID"
  +          }
  +        }
  +      }
  +    }'
  +    ```
   
   ## <a id="how-it-works"></a> How It Works
   
  
positive.code: 
  	```
  	cf v3-zdt-push APP-NAME
  	``` 
  <p class="note warning"><strong>Warning:</strong> Ensure that you understand the limitations of this feature before running the command. For more information, see <a href="#limitations">Limitations</a>.</p>
  
  For more information about this command, see [How It Works](#how-it-works). 
  
negative.code: For more information, see <a href="../../cf-cli/v7.html">Upgrading to cf CLI v7 (Beta)</a>. 
  </div>
  
  This topic describes how developers use beta Cloud Foundry Command Line Interface (cf CLI) commands or the Cloud Controller API (CAPI) to push their apps using a rolling deployment. 
  
  For information about the traditional method for addressing app downtime while pushing app updates, see [Using Blue-Green Deployment to Reduce Downtime and Risk](./blue-green.html).   
  
  
  ## <a id="prerequisites"></a> Prerequisites
  
  The procedures in this topic require one of the following:
  
  * **cf CLI v7**: 
  	* You must have the cf CLI v7. While in beta, cf CLI v7 is only tested against the latest CAPI release candidate.
  