delta/openstack/python-heatclient.git, branch 0.2.6

Add back --token-only for invocation compatibility

2013-12-04T22:08:19+00:00

This unused option should remain so that scripts that
use it do not break. It is suppressed so it will not
appear in the help.

Closes-Bug:1250731

Change-Id: I1180d8797d1e4c79dba92952931311cce50a1d3f

Add --include-pass option for grizzly backwards compat

2013-12-04T22:08:13+00:00

Set X-Auth-User, X-Auth-Key on all stack commands to allow the
latest python-heatclient to work on grizzly heat.

Partial-Bug:1250731

Change-Id: I29d4785cf3520e809252b5aeab25cf471a88cde8

Merge "Fix i18n error when resource-name is non-english"

2013-12-04T10:36:08+00:00

Revert "Don't call credentials_headers() twice"

2013-12-03T14:41:45+00:00

When we create or update a stack, when deferred_auth_method=password
(which is the default in heat.conf), the client must pass the username
and password, even if they don't need to for authentication (ie
they're passing a token). Otherwise there's no username and password
in the context to store, and the engine validation in
heat/engine/service.py::_validate_deferred_auth_context fails.

No such issue exists when deferred_auth_method=trusts, which is why
this problem was missed during testing of the patch being reverted.

Note some fixup in addition to the revert was required to make the
tests pass, as ShellTestToken and ShellTestStandaloneToken now require
username/password set in the fake env.

This reverts commit a7ba3c323b16227e0ba2527f21bc89625f125234
Change-Id: I0e7bc3f748022c2bf5ef7ef6dfe4d97953e3fcab

Merge "Honor endpoint_type when requesting keystone for a token"

2013-11-28T10:31:03+00:00

Merge "Make tokens work with --os-no-client-auth"

2013-11-28T08:58:52+00:00

Merge "test_shell test current not deprecated options"

2013-11-28T08:58:51+00:00

Merge "Fix shell operation with --os-auth-token"

2013-11-28T08:47:39+00:00

Merge "use correct url on Windows platform"

2013-11-28T01:01:46+00:00

Make tokens work with --os-no-client-auth

2013-11-27T19:13:06+00:00

Currently --os-no-client-auth assumes you'll only ever want to pass
a username and password to the standalone auth_password middleware,
but it's also valid to pass a token and endpoint, which can then
be used to either connect to a normal (non-standalone) Heat without
needing the client to connect to keystone, or pass a token to custom
auth middleware in standalone mode where tokens are accepted.

e.g:

heat --os-no-client-auth
      --heat-url http://127.0.0.1:8004/v1/
      --os-auth-token  stack-list

Change-Id: Ie22c85ba5b3b987505f4d6204b4dd6ff03e0d912
Closes-Bug: #1252248