system-config/playbooks/roles/letsencrypt-create-certs/handlers
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
..
main.yaml Upgrade to Keycloak 23.0 2024-02-06 05:33:37 +00:00
restart_apache.yaml Gracefully restart Apache after cert replacements 2020-01-14 20:20:43 +00:00
restart_gitea.yaml Manage opendev.org cert with LE 2019-11-18 12:07:10 -08:00
restart_graphite.yaml Graphite container deployment 2020-07-03 07:17:28 +10:00
restart_jitsi_meet.yaml Add meetpad server 2020-03-25 07:44:24 -07:00
restart_zuul_registry.yaml Manage insecure-ci-registry cert with LE 2020-01-13 15:20:20 -08:00
touch_file.yaml Use handlers for letsencrypt cert updates 2019-05-14 08:14:51 +10:00