e259163d56
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 a7ba3c323b
Change-Id: I0e7bc3f748022c2bf5ef7ef6dfe4d97953e3fcab
Python bindings to the Heat orchestration API
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).
Development takes place via the usual OpenStack processes as outlined in the OpenStack wiki. The master repository is on GitHub.
See release notes and more at http://docs.openstack.org/developer/python-heatclient/.