heat resource-list --nested-depth parent_resource is ambiguous
Bug #1467332 reported by
Steve Baker
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-heatclient |
Fix Released
|
High
|
Steve Baker |
Bug Description
Running the following
heat resource-list --nested-depth <DEPTH> <STACK>
results in a extra column parent_resource which includes the name of the parent resource. However when there are many ResourceGroup resources in the template, there will be many parent resources named '0'. This leads to ambiguity in what argument to use for "heat resource-show" commands.
I think the fix would be for the parent_resource to display the physical_
Changed in python-heatclient: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in python-heatclient: | |
status: | Triaged → In Progress |
Changed in python-heatclient: | |
status: | In Progress → Fix Committed |
Changed in python-heatclient: | |
milestone: | none → 0.7.0 |
Changed in python-heatclient: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Actually, heat event-list --nested-depth adds a stack_name column. To be consistent, resource-list should do the same. The stack name can also be used as the first argument to "heat resource-show"