system-config/playbooks/roles/keycloak/handlers/restart_keycloak.yaml
Jeremy Stanley f477e35561 Upgrade to Keycloak 23.0
This includes a switch from the "legacy" style Wildfly-based image
to a new setup using Quarkus.

Because Keycloak maintainers consider H2 databases as a test/dev
only option, there are no good migration and upgrade paths short of
export/import data. Go ahead and change our deployment model to rely
on a proper RDBMS, run locally from a container on the same server.

Change-Id: I01f8045563e9f6db6168b92c5a868b8095c0d97b
2024-02-06 05:33:37 +00:00

16 lines
564 B
YAML

- name: keycloak check for running containers
command: pgrep -f quarkus
ignore_errors: yes
register: quarkus_pids
- name: keycloak restart containers if running
# Also makes sure the containers weren't just restarted by an image update
when: quarkus_pids.rc == 0 and "is up-to-date" in keycloak_dcup.stderr
block:
- name: down containers
shell:
cmd: docker-compose -f /etc/keycloak-compose/docker-compose.yaml down
- name: up containers
shell:
cmd: docker-compose -f /etc/keycloak-compose/docker-compose.yaml up -d