From c1adb7746132d6e7425c0a1bca7de970a7dde9db Mon Sep 17 00:00:00 2001
From: TommyLike <tommylikehu@gmail.com>
Date: Tue, 28 Nov 2017 16:28:15 +0800
Subject: [PATCH] Update 'force' parameter for volume delete API

Parameter 'force' is used in the path rather than
body, update the document.

Change-Id: I2c79d7d64b5f3c48a147410d93ae687ac0eb3cdc
---
 api-ref/source/v3/parameters.yaml | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/api-ref/source/v3/parameters.yaml b/api-ref/source/v3/parameters.yaml
index 0a9381428de..6be99874cba 100644
--- a/api-ref/source/v3/parameters.yaml
+++ b/api-ref/source/v3/parameters.yaml
@@ -55,6 +55,14 @@ encryption_id:
   in: path
   required: true
   type: string
+force_5:
+  description: |
+    Indicates whether to force delete a volume even if
+    the volume is in deleting or error_deleting. Default is ``false``.
+  in: path
+  required: false
+  type: boolean
+  min_version: 3.23
 group_id:
   description: |
     The ID of the group.
@@ -1072,14 +1080,6 @@ force_4:
   in: body
   required: false
   type: boolean
-force_5:
-  description: |
-    Indicates whether to force deletes a volume even if
-    the volume is in deleting or error_deleting. Default is ``false``.
-  in: body
-  required: false
-  type: boolean
-  min_version: 3.23
 free_capacity:
   description: |
     The amount of free capacity for the back-end