summaryrefslogtreecommitdiff
path: root/keystoneclient/tests
Commit message (Collapse)AuthorAgeFilesLines
* Merge "Add CRUD support for application credentials"3.15.0Zuul2018-01-241-0/+116
|\
| * Add CRUD support for application credentialsColleen Murphy2018-01-231-0/+116
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Add support for creating, reading, and deleting application credentials. Application credentials do not support updating. Keystoneclient does not handle authentication with application credentials. This is done in keystoneauth. Additional work will be needed in python-openstackclient to support both CRUD and auth for application credentials. bp application credentials Change-Id: I21214238deac2c45f2f2d666287c2ae106955ab1
* | Add system role functionalityLance Bragstad2018-01-231-1/+73
|/ | | | | | | | | This commit adds the necessary bits to be able to use system role assignments from python-keystoneclient. bp system-scope Change-Id: Iecbcbf020a15f2bec777334c648d4477f89f3b2c
* Add project tags to keystoneclientSamuel Pilla2017-12-203-2/+342
| | | | | | | | | | | | | | | | | | Adds the client functionality for the following project tag calls: - Create a project tag on a project - Check if a project tag exists on a project - List project tags on a project - Modify project tags on a project - Delete a specific project tag on a project - Delete all project tags on a project Co-Authored-By: Jess Egler <jess.egler@gmail.com> Co-Authored-By: Rohan Arora <ra271w@att.com> Co-Authored-By: Tin Lam <tin@irrational.io> Partially Implements: bp project-tags Change-Id: I486b2969ae0aa2638842d842fb8b0955cc086d25
* Remove functional tests for v2.0 APIRodrigo Duarte Sousa2017-11-144-61/+0
| | | | Change-Id: I207b716e47893931e79e3758abc2bd879917f340
* Use generic user for both zuul v2 and v3Nam Nguyen Hoai2017-10-171-3/+3
| | | | | | | Zuul v2 uses 'jenkins' as user, but Zuul v3 uses 'zuul'. Using $USER solves it for both cases. Change-Id: I42cfcd4d8dee2ff3a99e42a5a64f3c38163972b8
* Remove use of positional decoratorMorgan Fainberg2017-08-071-5/+0
| | | | | | | | | The positional decorator results in poorly maintainable code in a misguided effort to emulate python3's key-word-arg only notation and functionality. This patch removes keystoneclient's dependance on the positional decorator. Change-Id: I9e691cc8b0c04992f4a8dabd67e1b413d3220d23
* Merge "Add support for endpoint group filtering"Jenkins2017-06-224-10/+246
|\
| * Add support for endpoint group filteringEnrique Garcia Navalon2017-04-134-10/+246
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The following API calls are made available: - GET /OS-EP-FILTER/projects/{project_id}/endpoint_groups - GET /OS-EP-FILTER/endpoint_groups/{endpoint_group_id}/projects - PUT /OS-EP-FILTER/endpoint_groups/{endpoint_group}/projects/{project_id} - HEAD /OS-EP-FILTER/endpoint_groups/{endpoint_group}/projects/{project_id} - DELETE /OS-EP-FILTER/endpoint_groups/{endpoint_group}/projects/{project_id} Co-Authored-By: Samuel de Medeiros Queiroz <samueldmq@gmail.com> Closes-Bug: #1641674 Change-Id: Idf938267479b5b8c50c9aa141c3c2770c2d69839
* | Add support for specifying role ids when creating trustKristi Nikolla2017-06-161-0/+16
| | | | | | | | | | Change-Id: I38e0ac35946ee6e53128babac3ea759a380572e0 Partial-Bug: 1696111
* | Merge "Replace six.iteritems() with .items()"Jenkins2017-06-1313-24/+15
|\ \
| * | Replace six.iteritems() with .items()M V P Nitesh2017-04-0313-24/+15
| |/ | | | | | | | | | | | | | | | | | | | | | | 1.As mentioned in [1], we should avoid using six.iteritems to achieve iterators. We can use dict.items instead, as it will return iterators in PY3 as well. And dict.items/keys will more readable. 2.In py2, the performance about list should be negligible, see the link [2]. [1] https://wiki.openstack.org/wiki/Python3 [2] http://lists.openstack.org/pipermail/openstack-dev/2015-June/066391.html Change-Id: I18a6890935ebdbb589269379f21a0dd47d07eb3a
* | Stop using oslotest.mockpatchChangBo Guo(gcb)2017-05-031-8/+8
|/ | | | | | This module has been deprecated in favor of native fixtures. Change-Id: I8fa00396f64d81eba807b2c6cbf4ae810447c59b
* Fix failing PY2 and PY3 gate jobsdineshbhor2017-03-222-2/+2
| | | | | | | | Please refer: http://logs.openstack.org/43/446943/1/check/gate-python-keystoneclient-python27-ubuntu-xenial/84b965d/console.html Closes-Bug: #1673761 Change-Id: Iefa74ffe8642f039a115e9ff4416c8f72d299317
* Merge "Add support for endpoint group CRUD"Jenkins2017-02-143-0/+166
|\
| * Add support for endpoint group CRUDSamuel de Medeiros Queiroz2017-02-113-0/+166
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The following API calls are made available: - POST /OS-EP-FILTER/endpoint_groups - GET /OS-EP-FILTER/endpoint_groups/{endpoint_group_id} - HEAD /OS-EP-FILTER/endpoint_groups/{endpoint_group_id} - PATCH /OS-EP-FILTER/endpoint_groups/{endpoint_group_id} - DELETE /OS-EP-FILTER/endpoint_groups/{endpoint_group_id} - GET /OS-EP-FILTER/endpoint_groups Partial-Bug: #1641674 Change-Id: I285eefe82152b178268f671e8800a0ff8c1511e4
* | Use https for *.openstack.org referencesEric Brown2017-02-054-9/+10
| | | | | | | | | | | | | | The openstack.org pages now support https and our references to the site should by default be one signed by the organization. Change-Id: Ia6cdaf7fabd1c355df002aa07b0695610dde9cd1
* | Merge "Fix boto version strip regex"Jenkins2017-01-271-0/+39
|\ \
| * | Fix boto version strip regexMarounMaroun2017-01-271-0/+39
| | | | | | | | | | | | | | | | | | | | | | | | the current regex pattern will match incorrect strings like: Boto/2x0t2 Change-Id: I260f4e0d98f082172a3a67a1fbaa05da5369ea49 Closes-Bug: #1658639
* | | Allow Multiple Filters of the Same KeySamuel Pilla2017-01-241-0/+23
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Before, the way filters were passed in would not allow filtering on the same key. For example: keystone.users.list(name__contains='test', name__contains='user') This fails because of how kwargs handles key/value pairs. This patch allows using multiple values for the same filter. Example: keystone.users.list(name__contains=['test', 'user']) Specifying the only one filter value is still functional as expected. Co-Authored-By: Jeffrey Augustine <ja224e@att.com> Partially-Implements: bp pci-dss-query-password-expired-users Change-Id: I89cecf7e18974e7860ba0925840d6264168eabcb
* | Fix response body being omitted in debug mode incorrectlyTin Lam2017-01-171-0/+10
| | | | | | | | | | | | | | | | | | | | In debug mode, when a response's header Content-Type is set to "application/json" with a parameter, i.e., "application/json; charset=UTF-8". This patch set ignores the additional parameter and only match the mimetype. Change-Id: Ie8fcb1061e0e49b039436947524cfdc704c83846 Closes-Bug: #1656981
* | Only log application/json in session to start3.9.0Steve Martinelli2017-01-101-30/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | When whitelisting content types to debug print from session we chose application/json and application/text. application/text is not a real mime type, text is typically text/plain. Rather than guess at mime types only print application/json to start with, but make it easy for additional types to be added later. Adapted from keystoneauth: Ica5fee076cdab8b1d5167161d28af7313fad9477 Related-Bug: 1616105 Change-Id: Ieaa8fb3ea8d25e09b89498f23b70b18c0f6153f1
* | X-Serivce-Token should be hashed in the logTin Lam2017-01-091-1/+2
| | | | | | | | | | | | | | | | | | | | Currently, logs display the hash values of X-Auth-Token, Authorization, and X-Subject-Token, but not the value of the X-Service-Token. This patch set adds the X-Service-Token to the list of header fields to be hashed for logging purposes. Change-Id: Iaa3a27f4b6c3baf964fa0c71328ffe9df43b2c0a Closes-Bug: #1654847
* | Merge "Do not log binary data during request"Jenkins2017-01-081-7/+4
|\ \
| * | Do not log binary data during requestSteve Martinelli2017-01-061-7/+4
| |/ | | | | | | | | | | | | | | | | | | Do not log binary data during debug logging of a session. Replace the binary data with the string <binary_data> instead. sort of a backport of: I5184002f3a21c5e0ee510b21b9a7884c8dccd1e3 Change-Id: I07ddbc3967f297597542f1975004d94c490f6e6b Related-Bug: 1616105
* | Merge "remove hacking checks from keystoneclient"Jenkins2017-01-064-148/+0
|\ \
| * | remove hacking checks from keystoneclientSteve Martinelli2017-01-064-148/+0
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | the only hacking check in keystoneclient is related to older versions of oslo libraries, which are no longer supported by keystoneclient, for example: $ pip freeze | grep oslo.utils oslo.utils==3.18.0 $ python >>> import oslo.utils Traceback (most recent call last): File "<stdin>", line 1, in <module> ImportError: No module named oslo.utils >>> import oslo_utils >>> Let's just remove the hacking check since theres no way someone could incorrectly import the older versions. Closes-Bug: 1652458 Signed-off-by: Adam Williamson <awilliam@redhat.com> Change-Id: I14165903b46d2fc26e8c9de591917893f58516db
* | Merge "Prevent MemoryError when logging response bodies"Jenkins2017-01-052-10/+59
|\ \ | |/ |/|
| * Prevent MemoryError when logging response bodiesTobias Diaz2017-01-052-10/+59
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Response bodies are loaded into memory prior to being logged. Loading huge response bodies may result in a MemoryError. This patch proposes that only JSON and TEXT responses be logged, i.e when the Content-Type header is application/json or application/text. Responses that do not include or have a different Content-Type header will have their body omitted. This is a sort of backport of the fix for keystoneauth sessions, see I93b6fff73368c4f58bdebf8566c4948b50980cee Co-Authored-By: Samuel de Medeiros Queiroz <samueldmq@gmail.com> Closes-bug: 1616105 Change-Id: I8f43eee3a0b35041c6cf672e476f8151cf2f8d14
* | re-work inference rule bindingsSteve Martinelli2016-12-183-44/+201
| | | | | | | | | | | | | | | | | | | | | | | | | | | | - At least one API was not implemented (list_implied_roles) - the tests were lacking assertions and proper mocked responses - some of the functionality just didn't work (see bug) - returning Role objects instead of InferenceRule objects Related commits: - I80a40e88b571fe9b0eca3af8b705ea79f28eb904 - I66e863fb83f8dfcca2c48116d4377df060f402c3 Closes-Bug: 1647934 Change-Id: I7b449a93d7d4d3eb9ca857f6c1f78f884bad2534
* | Merge "Deprecate the generic client"Jenkins2016-12-081-0/+1
|\ \
| * | Deprecate the generic clientJamie Lennox2016-12-071-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The generic client has been around and unused for a really long time. I dont think it works at all and was never updated to support V3 concepts. Realistically we can probably just remove it and noone will notice, but give it a quick deprecation cycle. Closes-Bug: #1647930 Change-Id: Ie68c8995275bcd55aede49d8f4af4e0d172de089
* | | Use assertIsNone(...) instead of assertEqual(None, ...)chenaidong12016-12-082-2/+2
|/ / | | | | | | | | | | | | | | | | | | | | Refer to:http://docs.openstack.org/developer/hacking/#unit-tests-and-assertraises [H203] Use assertIs(Not)None to check for None (off by default) Unit test assertions tend to give better messages for more specific assertions. As a result, assertIsNone(...) is preferred over assertEqual(None, ...) and assertIs(None, ...) Change-Id: I4e60f3f7f3557080669b98cb48627acc40a72606
* | Refactor test_projectsRodrigo Duarte Sousa2016-12-051-37/+36
| | | | | | | | | | | | | | Do not reuse the environment's domain and project, create new ones for the tests. Change-Id: I91a5c1b42c0b31f548c1154a4ef028f45cf1cd24
* | Refactor test_credentialsRodrigo Duarte Sousa2016-12-051-13/+18
| | | | | | | | | | | | | | Do not reuse client's domain, create a new one to be used only by the test, which is destroyed later. Change-Id: I4e3bb11a92535650317a30e6a1854bfd161ee93f
* | skip failing functional testSteve Martinelli2016-12-041-0/+3
| | | | | | | | Change-Id: If3894679d21709ab813b4675c4bc721a3987596a
* | Merge "Fix missing service_catalog parameter in Client object"3.8.0Jenkins2016-12-012-0/+16
|\ \
| * | Fix missing service_catalog parameter in Client objectMikhail Nikolaenko2016-08-052-0/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Return None if service_catalog parameter does not exist. service_catalog is the property and it is not initialized on object creation. service_catalog tries to get value from auth_ref and raises AttributeError exception if auth_ref is not initialized. It worked before we introduced sessions, because authentication happened on client instantiation. Now, when sessions are used, auth_ref is not initialized until the first request. This change adds try-catch block in service_catalog property to catch this error. Change-Id: I58eb888f0989241f9e5626564bd48d901b324d36 Closes-Bug: #1508374
* | | Merge "Pass allow_expired to token validate"Jenkins2016-11-291-0/+13
|\ \ \
| * | | Pass allow_expired to token validateJamie Lennox2016-11-291-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Allow passing the allow_expired flag to v3 token validation to support extended service to service communication. Implements bp: allow-expired Change-Id: Ia1763fedc1838ad3c58c7f8f98f00b7eaad55a5c
* | | | Replace 'assertFalse(a in b)' with 'assertNotIn(a, b)'howardlee2016-11-182-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | Trivial fix. Change-Id: I818245eaa9e63322b1c6de049368aa4e09b01b4b
* | | | Refactor test_domain_configsRodrigo Duarte Sousa2016-11-161-13/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Do not reuse the environment domain, create a new one to be fully controlled by the test cases. Change-Id: Idb894da724e252b01405fc937c021fd8981ee090
* | | | Support domain-specific configuration managementHenry Nash2016-11-023-0/+214
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Provide support for the domain-specific configuration storage available via the REST API. Domain configs are JSON blobs and we have fine grained control on them via the Identity API. This fine grained control is not defined yet in the client, though - for now, we can manage everything like Python dictionaries and use operations like "update" whenever we want to delete a specific group or option. This approach is similar to what is done in the federation mapping API to handle mapping rules. Functional tests are also included, this is useful to check if the new feature works in an integration environment. Co-Auhtored-By: Henry Nash <henryn@linux.vnet.ibm.com> Co-Authored-By: Rodrigo Duarte <rduartes@redhat.com> Closes-Bug: 1433306 Partially Implements: blueprint domain-config-ext Change-Id: Ie6795b8633fed38c58b79250c11c9a045b7f95a4
* | | Merge "TrivialFix: Using assertIsNone() instead of assertEqual(None)"Jenkins2016-10-201-1/+1
|\ \ \
| * | | TrivialFix: Using assertIsNone() instead of assertEqual(None)Anh Tran2016-09-271-1/+1
| | | | | | | | | | | | | | | | Change-Id: I1e3c101b6d8f21bbf98c98f5451334cc1b524d5b
* | | | Merge "Use exceptions from Keystoneauth"Jenkins2016-10-146-14/+18
|\ \ \ \
| * | | | Use exceptions from KeystoneauthJamie Lennox2016-08-246-14/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As keystoneclient and other services rely more on keystoneauth we should assume that keystoneauth is our base auth library, not keystoneclient and start to default to the objects provided from there. This will make it easier to remove these objects when the time comes. For the session independant parts of keystoneclient we should use the exception names as provided by keystoneauth instead of the aliases in keystoneclient. Change-Id: Ic513046f8398a76c244e145d6cc3117cdf6bb4cd
* | | | | Merge "Use AUTH_INTERFACE object from keystoneauth"Jenkins2016-10-052-6/+7
|\ \ \ \ \ | |/ / / /
| * | | | Use AUTH_INTERFACE object from keystoneauthJamie Lennox2016-08-242-6/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As keystoneclient and other services rely more on keystoneauth we should assume that keystoneauth is our base auth library, not keystoneclient and start to default to the objects provided from there. This will make it easier to remove these objects when the time comes. Use the AUTH_INTERFACE special object from keystoneauth in most places. This uses it everywhere that is actually session independant. For example it is not changed within the keystoneclient auth plugins themselves as they are directly compatible with keystoneauth. Change-Id: Ibc1224fca98c852106feb78c624b0b2f22b3a19d
* | | | | Merge "Use fixtures from keystoneauth"Jenkins2016-10-0518-22/+28
|\ \ \ \ \ | |/ / / /
View Lorry Controller Status