Go to file
Crag Wolfe c1e793f3b8 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
2017-01-28 01:04:29 -05:00
2016-11-12 19:23:34 +05:30
2016-11-12 19:23:26 +05:30
2015-10-22 15:37:18 -04:00
2012-12-02 17:48:42 +00:00
2015-05-12 03:44:29 -04:00
2014-12-10 12:11:48 +02:00
2012-10-10 08:55:03 +13:00
2016-11-25 17:17:23 +01:00
2016-09-09 10:03:28 +00:00
2015-09-18 16:42:10 +00:00

Team and repository tags

image

python-heatclient

Latest Version

Downloads

OpenStack Orchestration API Client Library

This is a client library for Heat built on the Heat orchestration API. It provides a Python API (the heatclient module) and a command-line tool (heat).

Description
OpenStack Orchestration (Heat) Client
Readme 14 MiB
Languages
Python 100%