From a77af0076f7fbcb3420354dffa0c604f25e369c1 Mon Sep 17 00:00:00 2001 From: Takashi NATSUME Date: Fri, 22 Dec 2017 07:58:46 +0900 Subject: [PATCH] api-ref: Fix parameter order in rebuild It is a follow-up for If01b2dcfa9df8c0e80ad1da65115204fe321891b. The 'progress' parameter has been changed to an optional parameter in If01b2dcfa9df8c0e80ad1da65115204fe321891b. Optional parameters should be after required parameters. So fix parameter order in rebuild action. And fix 'adminPass' as well. Change-Id: I38e0cdd73e9b81b5c4c8bd69c1139f99db3c7773 --- api-ref/source/servers-actions.inc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/api-ref/source/servers-actions.inc b/api-ref/source/servers-actions.inc index 16c7a46104..648bc3c427 100644 --- a/api-ref/source/servers-actions.inc +++ b/api-ref/source/servers-actions.inc @@ -505,7 +505,6 @@ Response - accessIPv4: accessIPv4 - accessIPv6: accessIPv6 - addresses: addresses_obj - - adminPass: adminPass_response - created: created - flavor: flavor_server - flavor.id: flavor_id_body_2_46 @@ -528,11 +527,12 @@ Response - metadata: metadata_object - name: server_name - OS-DCF:diskConfig: disk_config - - progress: progress - status: server_status - tenant_id: tenant_id_body - updated: updated - user_id: user_id + - adminPass: adminPass_response + - progress: progress - locked: locked - description: server_description_resp - tags: tags