diff options
| author | Crag Wolfe <cwolfe@redhat.com> | 2017-01-28 00:37:47 -0500 |
|---|---|---|
| committer | Crag Wolfe <cwolfe@redhat.com> | 2017-01-28 01:04:29 -0500 |
| commit | c1e793f3b81403d32d665679001264716aa38505 (patch) | |
| tree | 8d7c4a99900a356e1797fb28826392175fc1aeb8 /test-requirements.txt | |
| parent | 17dd3068e4d6fc10236290cc082908c439bcfead (diff) | |
| download | python-heatclient-c1e793f3b81403d32d665679001264716aa38505.tar.gz | |
Don't always resolve outputs when showing a stack
* Whenever a stack is created/updated/adopted, a call to show the
stack is made. Do not resolve the outputs when showing the stack in
this case because:
* If we are not waiting (there is no --wait arg) for the stack to
complete after a create/update/adopt command and immediately
showing the stack, resolving the outputs is just incurring a
pointless processing hit on the server (ultimately heat-engine)
and delaying a response to the client.
* Whether we --wait or or not, we only show "short" stack info which
doesn't include outputs anyway. So, let's avoid the
processing/time overhead of resolving the outputs. (In theory,
with --wait we might want to show "long" output with stack outputs
afterwards, but that would be additional functionality that should
be handled in a different patch)
* Add the --no-resolve-outputs option to "stack show" which already
exists in the legacy heat stack-show command.
Change-Id: Id0661b11fd3cece0df3981488de6976219556d7e
Closes-Bug: #1659896
Closes-Bug: #1659899
Diffstat (limited to 'test-requirements.txt')
0 files changed, 0 insertions, 0 deletions