summaryrefslogtreecommitdiff
path: root/keystoneclient/fixture
Commit message (Collapse)AuthorAgeFilesLines
* Update hacking for Python3Andreas Jaeger2020-03-311-0/+2
| | | | | | | | | The repo is Python 3 now, so update hacking to version 3.0 which supports Python 3. Fix problems found. Change-Id: Ic161a8f88c28d88898863e5b9d9380016fbb0d08
* Merge "map fixtures to keystoneauth"Jenkins2016-05-235-878/+46
|\
| * map fixtures to keystoneauthSteve Martinelli2016-05-225-878/+46
| | | | | | | | | | | | | | 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 Pustchi2016-04-231-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
* use positional library instead of utilsSteve Martinelli2016-01-251-6/+7
| | | | | | swap instances of utils.positional with the positional library. Change-Id: Id8a9961e68d287a802f25512fc970829e9feb5c2
* Make __all__ immutableDolph Mathews2015-10-012-4/+4
| | | | | | | | | 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
* Use UUID values in v3 test fixturesJamie Lennox2015-07-251-0/+8
| | | | | | | | The fixtures will automatically stub UUID values for required token fields, so we can check for those returned values rather than specify fixed string values. Change-Id: I8a6cc675c6c8ee14772a38d8fc38475885ebc605
* Switch from deprecated isotimeBrant Knudson2015-06-303-5/+7
| | | | | | | | | | | | | | | | | oslo_utils.timeutils.isotime() is deprecated as of 1.6 so we need to stop using it. The deprecation message says to use datetime.datetime.isoformat() instead, but the format of the string generated by isoformat isn't the same as the format of the string generated by isotime. The string is used in tokens and other public APIs and we can't change it without potentially breaking clients. So the workaround is to copy the current implementation from oslo_utils.timeutils.isotime() to keystone.common.utils.isotime(). Change-Id: I34b12b96de3ea21beaf935ed8a9f6bae2fe0d0bc Closes-Bug: 1461251
* Cleanup fixture importsBrant Knudson2015-05-311-4/+9
| | | | | | | | | OpenStack hacking guidelines say to not import objects, only modules[1]. [1] http://docs.openstack.org/developer/hacking/#imports Change-Id: I6ccb7fda5c406458567bd20ccc1d673fca245191
* Add endpoint and service ids to fixturesJamie Lennox2015-04-172-6/+8
| | | | | | | The service catalog should contain an endpoint id and service id in the v3 token and an endpoint id in the v2 token. Change-Id: I8835bcb7c68ae8d0175b6f58a4750cd6e25fd84c
* Merge "Return None for missing trust_id in fixture"Jenkins2015-04-081-1/+1
|\
| * Return None for missing trust_id in fixtureJamie Lennox2015-03-241-1/+1
| | | | | | | | | | | | | | | | | | | | If the trust_id is unset it raises a KeyError. This is unusual from a python perspective (if nothing else it should be AttributeError) and different to all the other attributes of the fixture. Return None if no trust_id is set on the fixture. Change-Id: I15d33d77027a188fa47df18387c4610908f8e2d2
* | Expose audit_id via AccessInfoJamie Lennox2015-03-282-2/+59
|/ | | | | | | | The audit_id is now a standard part of the v2 and v3 tokens. Expose it via AccessInfo so that it is usable for services and middleware. Change-Id: I14ddcfee5434084ad9da73c384e6f456602fdd2b Closes-Bug: #1437129
* Using correct keyword for region in v3Sergey Kraynev2015-02-121-1/+2
| | | | | | | | | Keystone v3 and v2 have different keywords in endpoint dictionary. This patch adds ability for keystone client for correct work with old and new API. Change-Id: I886b4c7ac3cbe08ac1b88f490e9ca92a90256961 Closes-Bug: #1364463
* Switch from oslo.utils to oslo_utilsBrant Knudson2015-01-313-3/+3
| | | | | | | | oslo_utils moved out of the oslo namespace. bp drop-namespace-packages Change-Id: I72e67dc1f649ba137dd06f5ab7133858c6abd67d
* Correct documenting constructor parametersBrant Knudson2014-12-041-37/+29
| | | | | | | | | | When the docs are rendered to HTML, any docs on __init__ are not displayed. The parameters to the constructor have to be documented on the class rather than on the __init__ method. Also, corrected other minor issues in the same areas. Change-Id: Ic56da33f6b99fe5efb636c289e3c4e1569f0c84c
* Use oslo.utils and oslo.serializationSteve Martinelli2014-10-153-3/+6
| | | | | | | Left timeutils and strutils in openstack/common since they are used in openstack/common/apiclient and memorycache. Change-Id: Idb5f09c159d907dfba84cd1f7501f650318af7d9
* Handle federated tokensMarek Denis2014-09-172-0/+30
| | | | | | | | | | | | | 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
* fix typosDolph Mathews2014-09-081-1/+1
| | | | Change-Id: Ia850e62fe4c888365f5031cc8b7c7ad526600222
* Fix mistakes in token fixturesJamie Lennox2014-07-162-2/+2
| | | | | | | | | There are two small mistakes i discovered in the token fixtures. Fix these and add a bunch of new tests that would have caught them earlier. Closes-Bug: #1342513 Closes-Bug: #1342515 Change-Id: I7c07bd915fd84cc77cae0004220d8bb8d79bb082
* Merge "Add trust users to AccessInfo and fixture"Jenkins2014-07-111-1/+27
|\
| * Add trust users to AccessInfo and fixtureJamie Lennox2014-06-291-1/+27
| | | | | | | | | | | | | | A trust should always contain a trustee_user_id and a trustor_user_id. Expose these values via AccessInfo if available. Change-Id: Ic46a44300e6bf8aa694f1543d470c16fcac643fc
* | Merge "Add OAuth data to AccessInfo"Jenkins2014-07-091-1/+26
|\ \ | |/
| * Add OAuth data to AccessInfoJamie Lennox2014-06-301-1/+26
| | | | | | | | | | | | | | | | | | Allow access to the access_token_id and the consumer_id that are set as part of the Oauth authentication process. This only makes sense for V3 tokens, as Oauth cannot be used with v2. Change-Id: I9ac76f92acdfd6446a13f535b24e0a99f02f2eef
* | Add a fixture for Keystone version discoveryJamie Lennox2014-07-022-3/+277
|/ | | | | | | | 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
* Add issued handlers to auth_ref and fixturesJamie Lennox2014-06-192-6/+55
| | | | | | | | issued_at is a standard part of V2 and V3 tokens so add it to AccessInfo in a similar way to expiry. Also it should be included when generating tokens so include it in fixtures. Change-Id: I0d62d8ce6472466886751e10e98046b8e398e079
* Add role ids to the AccessInfoJamie Lennox2014-06-191-4/+9
| | | | | | Role Names are already there, add ids as well. Change-Id: Ie6f14a60b182ec2f4ab97c6ced564e63a2f5169a
* Create a V3 Token GeneratorJamie Lennox2014-04-172-1/+306
| | | | | | | | A token generator that can be used by other clients to generate consistent tokens in there test code. Change-Id: I05d2632b4c8290c2b1015996769340f0bea16f93 blueprint: share-tokens
* Don't use generic kwargs in v2 Token GenerationJamie Lennox2014-04-141-23/+22
| | | | | | | | | | | We need to allow for people adding other stuff to the tokens however it shouldn't be available in the standard case where for example a misspelt variable would be propagated. This is in line with how v3 is going to handle this same scenario. Change-Id: I1aad17893574ebc7c3a6b84f4d6ba1cd27932158 Closes-Bug: #1307278
* Create a test token generator and use itJamie Lennox2014-04-033-0/+207
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
View Lorry Controller Status