Re: [keycloak-user] initialising docker
Hi Tim,
We also struggle with this. What we do at the moment is we _always_ import the realm on
startup of our Keycloak Docker container. Our current idea is that we will not have any
runtime configuration changes in our realm at all, apart from filling the Keycloak caches.
The idea being that runtime configuration changes are not automatable. We store our users
and groups in LDAP/Active Directory and all realm configuration is stored in the realm
JSON file in Git and imported every time.
I was wondering: if you do change your realm configuration runtime how do you deal with
deployment automation? Is your idea to only import your realm definition once? If so, how
would you deal with automating realm configuration changes?
cheers
Edgar
On 12 Feb 2016, at 16:14, Tim Dudgeon <tdudgeon.ml(a)gmail.com>
wrote:
I've been struggling with a clean way to initialize the keycloak docker
container.
I need to import a realm definition, and the only way I can find is it
start the image with the import options, wait for this to complete so
that the database is populated and then to Ctrl-C out and to restart the
container proper, which is hardly automatable.
With 1.8 this also needs to include defining the admin user.
Is there a cleaner way of achieving this?
For instance, with the postgres docker images you just put any
initialisation *.sql or *.sh scripts in a specific directory and they
get executed first time the server starts.
Tim
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user