summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* | | Merge "Replace six.iteritems() with .items()"Jenkins2017-06-1318-35/+24
|\ \ \
| * | | Replace six.iteritems() with .items()M V P Nitesh2017-04-0318-35/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | | Merge "Fix html_last_updated_fmt for Python3"3.11.0Jenkins2017-06-071-2/+1
|\ \ \ \
| * | | | Fix html_last_updated_fmt for Python3Vu Cong Tuan2017-06-061-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | html_last_updated_fmt option is interpreted as a byte string in python3, causing Sphinx build to break. This patch makes it utf-8 string. In addition, changing Popen to check_output because check_output() will raise CalledProcessError if the called process returns a non-zero return code. It also makes the code look much better. Change-Id: If01f08216b4b252bd31029913e83fe945bf76866 Closes-Bug:#1693670
* | | | | Updated from global requirementsOpenStack Proposal Bot2017-06-022-2/+2
|/ / / / | | | | | | | | | | | | Change-Id: I7002c54da6b5f3905e5f9746b7aaf28d5ae79ba3
* | | | Moved release note to the correct pathKristi Nikolla2017-05-261-0/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Release note was accidentally added to keystoneclient/releasenotes instead of releasenotes Change-Id: Id8ec0b895fa8f42d60572077bd5fe49d9478ee10
* | | | Updated from global requirementsOpenStack Proposal Bot2017-05-231-1/+1
| | | | | | | | | | | | | | | | Change-Id: If0701b99b3b9371664c5295c81a64e7f77238ce5
* | | | Updated from global requirementsOpenStack Proposal Bot2017-05-171-1/+1
| | | | | | | | | | | | | | | | Change-Id: I5f10869789eb6797e4f601d7a73b469fbe08fea7
* | | | Merge "Remove log translations in python-keystoneclient"Jenkins2017-05-168-48/+33
|\ \ \ \
| * | | | Remove log translations in python-keystoneclientwingwj2017-03-218-48/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Log messages are no longer being translated. This removes all use of the _LE, _LI, and _LW translation markers to simplify logging and to avoid confusion with new contributions. See: http://lists.openstack.org/pipermail/openstack-i18n/2016-November/002574.html http://lists.openstack.org/pipermail/openstack-dev/2017-March/113365.html Change-Id: Ia77819cbb133903d20e821bff0c45766b11ef07b
* | | | | Merge "Stop using oslotest.mockpatch"Jenkins2017-05-161-8/+8
|\ \ \ \ \
| * | | | | Stop using oslotest.mockpatchChangBo Guo(gcb)2017-05-031-8/+8
| | |_|_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | This module has been deprecated in favor of native fixtures. Change-Id: I8fa00396f64d81eba807b2c6cbf4ae810447c59b
* | | | | Updated from global requirementsOpenStack Proposal Bot2017-05-151-1/+1
| | | | | | | | | | | | | | | | | | | | Change-Id: I4b2dae6b4fcb887dcc21bd6540109df6e9952a47
* | | | | Updated from global requirementsOpenStack Proposal Bot2017-05-031-2/+2
|/ / / / | | | | | | | | | | | | Change-Id: Iade6679462be48ae1714800be35049fa7dc56aa6
* | | | Remove unused logzlyqqq2017-04-252-8/+0
| |_|/ |/| | | | | | | | Change-Id: I1fe2c1703b03eb1c8458c53bdd208a91ababf941
* | | Updated from global requirementsOpenStack Proposal Bot2017-03-222-5/+5
| |/ |/| | | | | Change-Id: If701ef91dd5c67b39518ed073318bd5bcb1c3ada
* | 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
* | Updated from global requirementsOpenStack Proposal Bot2017-02-152-3/+3
| | | | | | | | Change-Id: I9bc8e5d548371825ef793c4b601d98b095b2b7e3
* | Merge "Add support for endpoint group CRUD"Jenkins2017-02-145-0/+310
|\ \
| * | Add support for endpoint group CRUDSamuel de Medeiros Queiroz2017-02-115-0/+310
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | Fix 12 warnings when building keystoneclient docsGage Hugo2017-02-095-7/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | While building keystoneclient docs, there are currently 12 warnings emitted that specify either: WARNING: more than one target found for cross-reference u'list' WARNING: more than one target found for cross-reference u'Auth' This change specifies the correct object for the docstring with "List" since there are many instances of "list" within keystoneclient and specifies the proper "Auth" object. With these changes, the warnings no longer appear. Change-Id: I4515429df38760700552d48fc570c03abf116f83
* | | Use https for *.openstack.org referencesEric Brown2017-02-0513-29/+30
| | | | | | | | | | | | | | | | | | | | | 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-272-1/+40
|\ \ \
| * | | Fix boto version strip regexMarounMaroun2017-01-272-1/+40
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | the current regex pattern will match incorrect strings like: Boto/2x0t2 Change-Id: I260f4e0d98f082172a3a67a1fbaa05da5369ea49 Closes-Bug: #1658639
* | | | Update reno for stable/ocataOpenStack Release Bot2017-01-252-0/+7
| | | | | | | | | | | | | | | | Change-Id: I285ff2b66eb8ff11acc58688269a9587d0721b25
* | | | Merge "Allow Multiple Filters of the Same Key"ocata-em3.10.0Jenkins2017-01-253-1/+33
|\ \ \ \ | |/ / / |/| | |
| * | | Allow Multiple Filters of the Same KeySamuel Pilla2017-01-243-1/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | | Updated from global requirementsOpenStack Proposal Bot2017-01-211-1/+1
|/ / / | | | | | | | | | Change-Id: Ia7be0de146563e59b7ba50cc9d27f9d790c8b25a
* | | Fix response body being omitted in debug mode incorrectlyTin Lam2017-01-172-2/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | Updated from global requirementsOpenStack Proposal Bot2017-01-161-1/+1
| | | | | | | | | | | | Change-Id: Id01542e6bd83908f1859a047ec49bc16de87c8a3
* | | Merge "Removes unnecessary utf-8 encoding"Jenkins2017-01-132-3/+0
|\ \ \
| * | | Removes unnecessary utf-8 encodingji-xuepeng2017-01-132-3/+0
| | | | | | | | | | | | | | | | Change-Id: Ide4cb14246394522e35929cf08978aaf5fa9eb59
* | | | Only log application/json in session to start3.9.0Steve Martinelli2017-01-103-36/+34
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-093-2/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-082-7/+9
|\ \ \ \
| * | | | Do not log binary data during requestSteve Martinelli2017-01-062-7/+9
| | |/ / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-065-149/+0
|\ \ \ \
| * | | | remove hacking checks from keystoneclientSteve Martinelli2017-01-065-149/+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 "Remove references to Python 3.4"Jenkins2017-01-062-2/+1
|\ \ \ \
| * | | | Remove references to Python 3.4Eric Brown2017-01-052-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Now that there exists only a gate job for Python 3.5 and not 3.4, we should remove those references to the 3.4 that is untested. Change-Id: Id32fca50f5f1834175b6003be61f2cc4c8b9aeeb
* | | | | Updated from global requirementsOpenStack Proposal Bot2017-01-051-1/+1
|/ / / / | | | | | | | | | | | | Change-Id: Ie02917c0904dfa52205acbd65fe3bbb867efcdb3
* | | | Merge "Prevent MemoryError when logging response bodies"Jenkins2017-01-054-14/+82
|\ \ \ \ | |/ / / |/| | |
| * | | Prevent MemoryError when logging response bodiesTobias Diaz2017-01-054-14/+82
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | | Merge "re-work inference rule bindings"Jenkins2016-12-215-131/+383
|\ \ \ \
| * | | | re-work inference rule bindingsSteve Martinelli2016-12-185-131/+383
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - 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
* | | | | Add Constraints supportTony Breeds2016-12-212-3/+36
|/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adding constraints support to libraries is slightly more complex than services as the libraries themselves are listed in upper-constraints.txt which leads to errors that you can't install a specific version and a constrained version. This change adds constraints support by also adding a helper script to edit the constraints to remove python-keystoneclient. Change-Id: I8933945ab8948c43022963ba6cff4d38cec5a04f
* | | | Updated from global requirementsOpenStack Proposal Bot2016-12-151-1/+1
| | | | | | | | | | | | | | | | Change-Id: I0cda41be17bf1e8f65819e7dc6aca10cc7bffd49
* | | | Merge "Deprecate the generic client"Jenkins2016-12-083-0/+13
|\ \ \ \
| * | | | Deprecate the generic clientJamie Lennox2016-12-073-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
View Lorry Controller Status