Steven Hardy d9e3b3d2cd 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		2014-03-12 15:18:12 +00:00
..
common	Rename --timeout global option and make it work	2014-03-10 18:21:10 +00:00
openstack	Merge "Update apiclient.base and reuse new functional"	2014-03-01 13:11:58 +00:00
tests	Deprecate create/adopt --create-timeout in favor of --timeout	2014-03-12 15:18:12 +00:00
v1	Deprecate create/adopt --create-timeout in favor of --timeout	2014-03-12 15:18:12 +00:00
__init__.py	Support --version for heatclient	2013-09-04 14:29:56 +08:00
client.py	Initial import	2012-10-10 08:55:03 +13:00
exc.py	Port to python requests	2014-02-07 14:52:22 -06:00
shell.py	Deprecate create/adopt --create-timeout in favor of --timeout	2014-03-12 15:18:12 +00:00