From cb31a83888cd93fcb12a7ac9a3e678ee7bb8ceeb Mon Sep 17 00:00:00 2001 From: Henry Nash Date: Tue, 24 Mar 2015 17:57:25 +0000 Subject: Support domain-specific configuration management 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 --- doc/source/using-api-v3.rst | 1 + 1 file changed, 1 insertion(+) (limited to 'doc') diff --git a/doc/source/using-api-v3.rst b/doc/source/using-api-v3.rst index 8e2093d..f0c82c5 100644 --- a/doc/source/using-api-v3.rst +++ b/doc/source/using-api-v3.rst @@ -8,6 +8,7 @@ Introduction The main concepts in the Identity v3 API are: * :py:mod:`~keystoneclient.v3.credentials` + * :py:mod:`~keystoneclient.v3.domain_configs` * :py:mod:`~keystoneclient.v3.domains` * :py:mod:`~keystoneclient.v3.endpoints` * :py:mod:`~keystoneclient.v3.groups` -- cgit v1.2.1