| 2013-07-15 16:00:19 |
JunJie Nan |
bug |
|
|
added bug |
| 2013-07-15 16:31:38 |
JunJie Nan |
affects |
heat |
python-heatclient |
|
| 2013-07-15 16:31:47 |
JunJie Nan |
python-heatclient: assignee |
|
JunJie Nan (nanjj) |
|
| 2013-07-16 01:47:46 |
JunJie Nan |
description |
1. heat stack-create -f heat-templates/hot/hello_world.yaml hot ...
2. heat template-show hot
It should show YAML format template but, actually, the template show JSON format.
The JSON format template can not be used to create stack again since it will skip hot translate logic. |
1. heat stack-create -f heat-templates/hot/hello_world.yaml hot ...
2. heat template-show hot
It should show YAML format template but, actually, the template show JSON format. |
|
| 2013-07-16 05:47:22 |
JunJie Nan |
description |
1. heat stack-create -f heat-templates/hot/hello_world.yaml hot ...
2. heat template-show hot
It should show YAML format template but, actually, the template show JSON format. |
To reproduce the problem:
1. heat stack-create -f heat-templates/hot/hello_world.yaml hot ...
2. heat template-show hot
It should show YAML format instead of JSON format. |
|
| 2013-07-16 05:48:18 |
JunJie Nan |
summary |
Hot template show cfn format after deploy |
Hot template show JSON format after deploy |
|
| 2013-07-16 05:56:19 |
OpenStack Infra |
python-heatclient: status |
New |
In Progress |
|
| 2013-07-16 08:43:26 |
JunJie Nan |
description |
To reproduce the problem:
1. heat stack-create -f heat-templates/hot/hello_world.yaml hot ...
2. heat template-show hot
It should show YAML format instead of JSON format. |
To reproduce the problem:
1. heat stack-create -f heat-templates/hot/hello_world.yaml hot ...
2. heat template-show hot
It should show YAML format instead of JSON format.
Why?
Normally end user use `heat template-show stack > mystack.template` to get latest template from stack, modify the template and do `heat update mystack.template stack`. It makes sense if we keep the format consistent between `heat template-show` and the deployed on. |
|
| 2013-07-16 21:24:02 |
Steve Baker |
python-heatclient: importance |
Undecided |
Medium |
|
| 2013-07-16 21:28:29 |
Steve Baker |
python-heatclient: milestone |
|
v0.2.4 |
|
| 2013-07-16 23:14:06 |
OpenStack Infra |
python-heatclient: status |
In Progress |
Fix Committed |
|
| 2013-07-17 00:37:57 |
JunJie Nan |
description |
To reproduce the problem:
1. heat stack-create -f heat-templates/hot/hello_world.yaml hot ...
2. heat template-show hot
It should show YAML format instead of JSON format.
Why?
Normally end user use `heat template-show stack > mystack.template` to get latest template from stack, modify the template and do `heat update mystack.template stack`. It makes sense if we keep the format consistent between `heat template-show` and the deployed on. |
To reproduce the problem:
1. heat stack-create -f heat-templates/hot/hello_world.yaml hot ...
2. heat template-show hot
It should show YAML format instead of JSON format.
Why?
Normally end user use `heat template-show stack > mystack.template` to get latest template from stack, modify the template and do `heat update mystack.template stack`. It makes sense if we keep the format consistent between `heat template-show` and the template deployed. |
|
| 2013-08-07 04:37:23 |
Steve Baker |
python-heatclient: status |
Fix Committed |
Fix Released |
|
