delta/openstack/python-keystoneclient.git/keystoneclient/fixture/__init__.py, branch 2.1.2 opendev.org: openstack/python-keystoneclient.git Make __all__ immutable 2015-10-01T18:18:13+00:00 Dolph Mathews dolph.mathews@gmail.com 2015-10-01T16:56:33+00:00 eb77abd77a25baa556de4df527404b907748d3c6 Using a mutable type implies that it's acceptable for the set of publicly-accessible attributes to be mutated at runtime, which defeats their intended purpose of documenting the public interface. Tuples are immutable. Change-Id: Ib3ab93224ba240040b08ece481ef5ba620c3f658 
Using a mutable type implies that it's acceptable for the set of
publicly-accessible attributes to be mutated at runtime, which defeats
their intended purpose of documenting the public interface. Tuples are
immutable.

Change-Id: Ib3ab93224ba240040b08ece481ef5ba620c3f658
Cleanup fixture imports 2015-05-31T15:27:01+00:00 Brant Knudson bknudson@us.ibm.com 2015-05-31T15:27:01+00:00 f756798c2a2f55c9db1b7493848225ade7878478 OpenStack hacking guidelines say to not import objects, only modules[1]. [1] http://docs.openstack.org/developer/hacking/#imports Change-Id: I6ccb7fda5c406458567bd20ccc1d673fca245191 
OpenStack hacking guidelines say to not import objects, only
modules[1].

[1] http://docs.openstack.org/developer/hacking/#imports

Change-Id: I6ccb7fda5c406458567bd20ccc1d673fca245191
Handle federated tokens 2014-09-17T19:46:49+00:00 Marek Denis marek.denis@cern.ch 2014-09-12T15:24:59+00:00 7006f9b0088eb1828f4da24b62e306b37eef79d2 Federated tokens don't include domains in the user object. Keystoneclient should be able to estimate whether the token is a federated one and, if so, don't expect user domain information. In case of the federated token keystoneclient returns None in response to user_domain_name and user_domain_id calls. Co-Authored-By: Steve Martinelli <stevemar@ca.ibm.com> Closes-Bug: #1346820 Change-Id: I3453275fa1b0a41b1c015b0c3a92895a77d69a41 
Federated tokens don't include domains in the user object.
Keystoneclient should be able to estimate whether the token is a
federated one and, if so, don't expect user domain information.
In case of the federated token keystoneclient returns None in response
to user_domain_name and user_domain_id calls.

Co-Authored-By: Steve Martinelli <stevemar@ca.ibm.com>

Closes-Bug: #1346820
Change-Id: I3453275fa1b0a41b1c015b0c3a92895a77d69a41
Add a fixture for Keystone version discovery 2014-07-02T03:28:01+00:00 Jamie Lennox jamielennox@redhat.com 2014-06-13T05:33:03+00:00 05f362dcb442a96dd7f33230d75b1f71235c2c64 As we push out the session and expect people to test with proper URL responses we should provide a means to create a correct Keystone version list to test with. Change-Id: I8309ab6cbc47ad159f3c6e018b60ff8c15c6d917 
As we push out the session and expect people to test with proper URL
responses we should provide a means to create a correct Keystone version
list to test with.

Change-Id: I8309ab6cbc47ad159f3c6e018b60ff8c15c6d917
Create a V3 Token Generator 2014-04-16T21:11:34+00:00 Jamie Lennox jamielennox@redhat.com 2014-03-07T06:23:25+00:00 ee49824fe70244977e8d5a9af36590fb7edbe59d A token generator that can be used by other clients to generate consistent tokens in there test code. Change-Id: I05d2632b4c8290c2b1015996769340f0bea16f93 blueprint: share-tokens 
A token generator that can be used by other clients to generate
consistent tokens in there test code.

Change-Id: I05d2632b4c8290c2b1015996769340f0bea16f93
blueprint: share-tokens
Create a test token generator and use it 2014-04-03T01:20:33+00:00 Jamie Lennox jamielennox@redhat.com 2014-03-07T03:20:40+00:00 d69461b18fcd05fdce63e98634cd6e7f102ff091 All the clients are currently storing samples of keystone tokens so that they can use them in testing. This is bad as they are often out of date or contain data that they shouldn't. Create a V2 Token generator and make use of that for generating tokens within our tests. Change-Id: I72928692142c967d13391752ba57b3bdf7c1feab blueprint: share-tokens 
All the clients are currently storing samples of keystone tokens so that
they can use them in testing. This is bad as they are often out of date
or contain data that they shouldn't.

Create a V2 Token generator and make use of that for generating tokens
within our tests.

Change-Id: I72928692142c967d13391752ba57b3bdf7c1feab
blueprint: share-tokens