Updated openstack/openstack
Project: openstack/python-heatclient  d9e3b3d2cdae60804851200ef96d9c8250bce210
null
Deprecate create/adopt --create-timeout in favor of --timeout

Replace the --create-timeout option with a more generic and intuitive
--timeout option, which can also later be used for update.

Since users may be using this option and it does currently work, leave
the old -c/--create-timeout option for now, but mark deprecated in the
usage and output a warning message if users use it.  To make this
warning visible the default loglevel is changed to WARNING.

Note neither timeout contains an integer default now, we rely on the
server-side default (which is 60mins anyway) as this make the fallback
to support the previous option easier and potentially to provide an
easier way to solve heat bug #1290603.

Partial-Bug: #1290456
Related-Bug: #1290603
Change-Id: Ia8c8d61b259ffa1f8a59d29a3e7fa7d9c128984f
Updated openstack/openstack
Project: openstack/python-heatclient  f12b1cd5fc2ce66d828eed731b347c33fb790a5c
null
Add timeout option to stack-update

The API spec says the PUT which handles stack-update accepts a
timeout_mins argument, so add CLI support for it, making the
interface consistent with create/adopt.  Note this argument
currently isn't respected by heat, ref bug #1290603

Change-Id: Ie8d51540d0d93be51966e60601fd02d635cdae09
Closes-Bug: #1290456
Related-Bug: #1290603