| 2016-06-10 01:03:04 |
Steve Baker |
description |
Currently heatclient builds the nested stack event list by doing recursive client-side event list calls for each stack. The REST API should support this natively so it can be implemented in a more efficient way. |
Currently heatclient builds the nested stack event list by doing recursive client-side event list calls for each stack. The REST API should support this natively so it can be implemented in a more efficient way.
The GET call to list events will support a nested_depth parameter. The response will have an additional links url with the ref 'root_stack' to indicate that this API supports nested_depth queries.
This has the following consequences for old/new combinations of
client/server
- new heatclient, new server - nested_depth param is set, server returns nested events
- new heatclient, old server - nested_depth param is set, server returns events with no root_stack, heatclient falls back to recursive event fetch
- old heatclient, new server - nested_depth param is never set, recursive event fetch works as before |
|
