From 6da62945bc8fe487c2058a802c26b2d79e1b32af Mon Sep 17 00:00:00 2001 From: Zane Bitter Date: Tue, 14 Jan 2020 16:33:45 -0500 Subject: [PATCH] Fix API docs for target_power_state response The API docs stated that the values of target_power_state in a Node State Summary are the same as the valid input values in a Change Node Power State request (i.e. they include "rebooting", "soft rebooting", and "soft power off"). However, in actuality these are all compressed to either "power on" or "power off" by the _calculate_target_state() function. Change-Id: I8c8b8c707102275a48233fc853acfb65f556946e Story: #2007089 Task: 38115 --- api-ref/source/parameters.yaml | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/api-ref/source/parameters.yaml b/api-ref/source/parameters.yaml index c2d15d54d7..66e066c523 100644 --- a/api-ref/source/parameters.yaml +++ b/api-ref/source/parameters.yaml @@ -1565,8 +1565,7 @@ supported_boot_devices: target_power_state: description: | If a power state transition has been requested, this field represents the - requested (ie, "target") state either "power on", "power off", "rebooting", - "soft power off" or "soft rebooting". + requested (ie, "target") state, either "power on" or "power off". in: body required: true type: string