delta/openstack/python-keystoneclient.git - opendev.org: openstack/python-keystoneclient.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	Merge "map fixtures to keystoneauth"	Jenkins	2016-05-23	1	-0/+13
\|\
\| *	map fixtures to keystoneauth	Steve Martinelli	2016-05-22	1	-0/+13
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	point to the latest fixtures in keystoneauth so we do not need to update code in two spots. Change-Id: I1e9ffdafd4dc06b84bc643e570dbea0132b47540
* \|	Fix D400 PEP257 violation.	Navid Pustchi	2016-04-23	1	-2/+3
\|/ \| \| \| \| \| \| \|	Currently tox ignores D400. D400: First line should end with a period. This change removes it and make keystoneclient docstrings compliant with it. Change-Id: I29ecb4c58bb03c0b9a3be0b7a74d18fb06a350f2
*	Make __all__ immutable	Dolph Mathews	2015-10-01	1	-2/+2
\| \| \| \| \| \| \| \| \|	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	Brant Knudson	2015-05-31	1	-4/+9
\| \| \| \| \| \| \| \| \|	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	Marek Denis	2014-09-17	1	-0/+2
\| \| \| \| \| \| \| \| \| \| \| \| \|	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	Jamie Lennox	2014-07-02	1	-3/+10
\| \| \| \| \| \| \| \|	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	Jamie Lennox	2014-04-17	1	-1/+2
\| \| \| \| \| \| \| \|	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	Jamie Lennox	2014-04-03	1	-0/+27
	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