openstack stack output show command output format is not consistent across multiple options
as given below:
manickan@mrkanag-os:~/workspace/hot-tutorials$ openstack stack output show test1 random_str
+--------------+----------------------------------+
| Field | Value |
+--------------+----------------------------------+
| description | No description given |
| output_key | random_str |
| output_value | 90DsmZUvliv0R1ZyhwG6R4tHKR7ICQ0B |
+--------------+----------------------------------+
manickan@mrkanag-os:~/workspace/hot-tutorials$ openstack stack output show test1 --all
+------------+--------------------------------------------------------+
| Field | Value |
+------------+--------------------------------------------------------+
| random_str | { |
| | "output_value": "90DsmZUvliv0R1ZyhwG6R4tHKR7ICQ0B", |
| | "output_key": "random_str", |
| | "description": "No description given" |
| | } |
+------------+--------------------------------------------------------+
Its always expected that the field list is know to user when 'show' command is used, when --all is used the field list is not consistent.
To provide -all options, better to give '--more' in 'openstack stack output list test1 --more', which will report addition column
'value' in addition to 'name', description'.
For inconsistent result formats, I think we can unify them into the format which displayed when using --all option.
For adding "--more" option in command output list, I think we do not need to do this for now. The reasons are:
1. The output list api just returned the key and description:
RESP BODY: {"outputs": [{"output_key": "status_code", "description": "No description given"}, {"output_key": "result", "description": "No description given"}, {"output_key": "stderr", "description": "No description given"}, {"output_key": "stdout", "description": "No description given"}]}
2. Users can use show command to see the value.