| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: I4b2dae6b4fcb887dcc21bd6540109df6e9952a47
|
|
|
|
| |
Change-Id: Iade6679462be48ae1714800be35049fa7dc56aa6
|
|
|
|
| |
Change-Id: I1fe2c1703b03eb1c8458c53bdd208a91ababf941
|
|
|
|
| |
Change-Id: If701ef91dd5c67b39518ed073318bd5bcb1c3ada
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Change-Id: I9bc8e5d548371825ef793c4b601d98b095b2b7e3
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| |
| |
| | |
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
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
the current regex pattern will match incorrect
strings like: Boto/2x0t2
Change-Id: I260f4e0d98f082172a3a67a1fbaa05da5369ea49
Closes-Bug: #1658639
|
| | |
| | |
| | |
| | | |
Change-Id: I285ff2b66eb8ff11acc58688269a9587d0721b25
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
|/ /
| |
| |
| | |
Change-Id: Ia7be0de146563e59b7ba50cc9d27f9d790c8b25a
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| | |
Change-Id: Id01542e6bd83908f1859a047ec49bc16de87c8a3
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Change-Id: Ide4cb14246394522e35929cf08978aaf5fa9eb59
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
|\ \ \ |
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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
|
|/ / /
| | |
| | |
| | | |
Change-Id: Ie02917c0904dfa52205acbd65fe3bbb867efcdb3
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- 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
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
| | |
| | |
| | |
| | | |
Change-Id: I0cda41be17bf1e8f65819e7dc6aca10cc7bffd49
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Do not reuse the environment's domain and project, create new ones for
the tests.
Change-Id: I91a5c1b42c0b31f548c1154a4ef028f45cf1cd24
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Do not reuse client's domain, create a new one to be used only by the
test, which is destroyed later.
Change-Id: I4e3bb11a92535650317a30e6a1854bfd161ee93f
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | | |
Change-Id: I943665eef62b3427e66e2f9c5f5f9d1088ff36ee
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
keystoneclient.tests.unit.test_cms.CMSTest.test_cms_verify
keystoneclient.tests.unit.test_cms.CMSTest.test_cms_verify_token_no_files
failing with: Command 'openssl' returned non-zero exit status 1
I think its OpenSSL >= 1.1 bug, which returns wrong exit code (1 instead of
2) if input file not exists.
Change-Id: I776596487f305c759b88c0d4c604571c33c6ef70
Closes-Bug: #1646858
|
| | |
| | |
| | |
| | | |
Change-Id: If3894679d21709ab813b4675c4bc721a3987596a
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Allow passing the allow_expired flag to v3 token validation to support
extended service to service communication.
Implements bp: allow-expired
Change-Id: Ia1763fedc1838ad3c58c7f8f98f00b7eaad55a5c
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This patch adds the team's and repository's badges to the README file.
The motivation behind this is to communicate the project status and
features at first glance.
For more information about this effort, please read this email thread:
http://lists.openstack.org/pipermail/openstack-dev/2016-October/105562.html
To see an example of how this would look like check:
https://gist.github.com/9ccb4a8d24c50452d5c816c357a4c220
Change-Id: I79ea8e8aafe99d729b7ee64899b6e7342afc40ee
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Trivial fix.
Change-Id: I818245eaa9e63322b1c6de049368aa4e09b01b4b
|