heat resource-list --nested-depth parent_resource is ambiguous

Bug #1467332 reported by Steve Baker
6
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_resource_id of the parent resource rather than the name (which in this case is the UUID of the nested stack that the resource is in) This allows parent_resource values to be used as the stack argument in "heat resource-show"

Changed in python-heatclient:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Steve Baker (steve-stevebaker) wrote :

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"

Changed in python-heatclient:
assignee: nobody → Steve Baker (steve-stevebaker)
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.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.