delta/openstack/python-keystoneclient.git/keystoneclient/tests/functional, branch pike-eol

Add support for endpoint group filtering

2017-04-13T17:19:39+00:00

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 

Closes-Bug: #1641674

Change-Id: Idf938267479b5b8c50c9aa141c3c2770c2d69839

Merge "Add support for endpoint group CRUD"

2017-02-14T16:09:39+00:00

Add support for endpoint group CRUD

2017-02-11T12:38:37+00:00

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

Allow Multiple Filters of the Same Key

2017-01-25T01:43:53+00:00

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 
Partially-Implements: bp pci-dss-query-password-expired-users
Change-Id: I89cecf7e18974e7860ba0925840d6264168eabcb

re-work inference rule bindings

2016-12-19T03:16:31+00:00

- 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

Refactor test_projects

2016-12-06T02:58:38+00:00

Do not reuse the environment's domain and project, create new ones for
the tests.

Change-Id: I91a5c1b42c0b31f548c1154a4ef028f45cf1cd24

Refactor test_credentials

2016-12-06T02:42:11+00:00

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 test

2016-12-04T03:28:12+00:00

Change-Id: If3894679d21709ab813b4675c4bc721a3987596a

Refactor test_domain_configs

2016-11-16T17:01:48+00:00

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 management

2016-11-02T17:03:41+00:00

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 
Co-Authored-By: Rodrigo Duarte 

Closes-Bug: 1433306

Partially Implements: blueprint domain-config-ext

Change-Id: Ie6795b8633fed38c58b79250c11c9a045b7f95a4