1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
community.general/tests/integration/targets/keycloak_userprofile
patchback[bot] 5f7a3ac896
[PR #8651/529af498 backport][stable-9] keycloak_userprofile: new module (#8848)
keycloak_userprofile: new module (#8651)

keycloak_userprofile: new keycloak module to manage user profiles (#8651)

(cherry picked from commit 529af4984c)

Co-authored-by: Eike Waldt <waldt@b1-systems.de>
2024-09-09 14:06:42 +02:00
..
meta [PR #8651/529af498 backport][stable-9] keycloak_userprofile: new module (#8848) 2024-09-09 14:06:42 +02:00
tasks [PR #8651/529af498 backport][stable-9] keycloak_userprofile: new module (#8848) 2024-09-09 14:06:42 +02:00
vars [PR #8651/529af498 backport][stable-9] keycloak_userprofile: new module (#8848) 2024-09-09 14:06:42 +02:00
aliases [PR #8651/529af498 backport][stable-9] keycloak_userprofile: new module (#8848) 2024-09-09 14:06:42 +02:00
readme.adoc [PR #8651/529af498 backport][stable-9] keycloak_userprofile: new module (#8848) 2024-09-09 14:06:42 +02:00

// 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:24.0.5 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:24.0.5 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 completely. While its active
it changes the server configuration in the following ways:

  * creating, modifying and deleting some keycloak userprofiles