mirror of
https://github.com/ansible-collections/community.general.git
synced 2024-09-14 20:13:21 +02:00
1462ed0b4a
keycloak_group: support keycloak subgroups (#5814)
* feat(module/keycloak_group): add support for ...
... handling subgroups
* added changelog fragment and fixing sanity ...
... test issues
* more sanity fixes
* fix missing version and review issues
* added missing licence header
* fix docu
* fix line beeing too long
* replaced suboptimal string type prefixing ...
... with better subdict based approach
* fix sanity issues
* more sanity fixing
* fixed more review issues
* fix argument list too long
* why is it failing? something wrong with the docu?
* is it this line then?
* undid group attribute removing, it does not ...
... belong into this PR
* fix version_added for parents parameter
---------
Co-authored-by: Mirko Wilhelmi <Mirko.Wilhelmi@sma.de>
(cherry picked from commit 7d3e6d1bb7)
Co-authored-by: morco <thegreatwiper@web.de>
27 lines
1.2 KiB
Text
27 lines
1.2 KiB
Text
// Copyright (c) Ansible Project
|
|
// GNU General Public License v3.0+ (see LICENSES/GPL-3.0-or-later.txt or https://www.gnu.org/licenses/gpl-3.0.txt)
|
|
// SPDX-License-Identifier: GPL-3.0-or-later
|
|
|
|
To be able to run these integration tests a keycloak server must be
|
|
reachable under a specific url with a specific admin user and password.
|
|
The exact values expected for these parameters can be found in
|
|
'vars/main.yml' file. A simple way to do this is to use the official
|
|
keycloak docker images like this:
|
|
|
|
----
|
|
docker run --name mykeycloak -p 8080:8080 -e KC_HTTP_RELATIVE_PATH=<url-path> -e KEYCLOAK_ADMIN=<admin_user> -e KEYCLOAK_ADMIN_PASSWORD=<admin_password> quay.io/keycloak/keycloak:20.0.2 start-dev
|
|
----
|
|
|
|
Example with concrete values inserted:
|
|
|
|
----
|
|
docker run --name mykeycloak -p 8080:8080 -e KC_HTTP_RELATIVE_PATH=/auth -e KEYCLOAK_ADMIN=admin -e KEYCLOAK_ADMIN_PASSWORD=password quay.io/keycloak/keycloak:20.0.2 start-dev
|
|
----
|
|
|
|
This test suite can run against a fresh unconfigured server instance
|
|
(no preconfiguration required) and cleans up after itself (undoes all
|
|
its config changes) as long as it runs through completly. While its active
|
|
it changes the server configuration in the following ways:
|
|
|
|
* creating, modifying and deleting some keycloak groups
|
|
|