mirror of
https://github.com/ansible-collections/community.general.git
synced 2024-09-14 20:13:21 +02:00
58a4610b61
Add keycloak_authz_permission module (#6321)
* Add keycloak_authz_permission module
* keycloak_authz_permission: add version_added metadata
Co-authored-by: Felix Fontein <felix@fontein.de>
* keycloak_authz_permission: assume changed=True on update operations
* keycloak_authz_permission: implement check_mode
* keycloak_authz_permission: move state queries into a dedicated _info module
* keycloak_authz_permission: bump version_added to 7.2.0
* keycloak_authz_permission: final fixes
Signed-off-by: Samuli Seppänen <samuli.seppanen@puppeteers.net>
* Update plugins/modules/keycloak_authz_permission_info.py
Co-authored-by: Felix Fontein <felix@fontein.de>
---------
Signed-off-by: Samuli Seppänen <samuli.seppanen@puppeteers.net>
Co-authored-by: Felix Fontein <felix@fontein.de>
(cherry picked from commit
|
||
---|---|---|
.. | ||
tasks | ||
vars | ||
aliases | ||
readme.adoc |
// 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