Incomplete detailed stack list

[Ladislav Smola]

https://github.com/openstack/heat/blob/b801f70505b8c797deb73e5c1148a56b5c24c4cd/heat/api/openstack/v1/stacks.py#L322

the detailed list has several issues

1. It's not documented in API reference
2. It does not accept query, e.g. show_nested
3. It doesn't return all details, e.g. outputs always return [], but heat output-list <stack_name> returns outputs

[Steve Baker (steve-stevebaker)]

heatclient doesn't seem to expose access to this api call either. I think this API call should be flagged as deprecated, for removal if we ever to a v2

[Ladislav Smola (lsmola)]

Well, wouldn't it be better to rather fix it? Detailed list is needed for our use case. Right now, we need to make an extra detail API call for each stack, which is very slow. Comparing to other services, detailed list should be present.

[Kent Wang (k.wang)]

Hi I tried `heat stack-show <name>' and it listed all the outputs
Can you provide a way to replicate the bug?

[Steve Baker (steve-stevebaker)]

Ladislav, I'm not sure of the history of having a detail list API call, but it might only be because the cloudformation API has one.

Another thing to consider in the fix vs deprecate is that a stack list detail call will parse every stack, which could cause quite some load on a heat engine.

It sounds like you have a need for a stack list detail call, what is missing from the stack-list call that you actually require?

[Ladislav Smola (lsmola)]

The detailed list was implemented as part of this bug https://bugs.launchpad.net/heat/+bug/1191117 But it didn't go all the way to support it fully. Yes, I expect detailed list will take longer time, but it should still be more effective, than extra API call per stack.

I think good start would be to return list with details from 'heat stack-show <name>', so we don't have to call details for each stack. This is usually what other OpenStack services do.

Would be nice to include also template to that list. Maybe switchable by another query param, so it is not in detailed list by default.

Then we do resource-list and event-list per each stack. But hopefully we will be able to call it just once with nested_depth and link it by stack_id?

[Steve Baker (steve-stevebaker)]

OK, lets fix it then. It also needs to implement paging and sorting if it doesn't already.

[Steve Baker (steve-stevebaker)]

adding python-heatclient so stack list details is exposed in the client lib too.