It's not a particular elegant way to import the realm, but it's the only way I can
think of unless we improve things in KC.
Your problem is that you're starting the server in the foreground, which causes the
"command" to never complete. If you look at for example bin/control the start()
function executes standalone.sh in the background, then it waits until the http port is
ready.
----- Original Message -----
From: "Christina Lau" <christinalau28(a)icloud.com>
To: keycloak-user(a)lists.jboss.org
Sent: Tuesday, 25 November, 2014 2:58:54 PM
Subject: [keycloak-user] Which action hook should I use to run Keycloak import on
Openshift?
Hi, I am trying to import realm into my Openshift Keycloak. I can import
successfully in my build action hook, but something is quite strange.
Because I am running ./standalone.sh to start the server, the openshift ssh
window is sitting in a strange state where it cannot carry on to finish the
rest of its life cycle.
$OPENSHIFT_HOMEDIR/wildfly/bin/standalone.sh
-Dkeycloak.migration.action=import -Dkeycloak.migration.provider=singleFile
-Dkeycloak.migration.file=$OPENSHIFT_HOMEDIR/app-root/repo/src/dsgapi.json
-Dkeycloak.migration.strategy=OVERWRITE_EXISTING
I think I am doing something wrong. Can you tell me how I should do this? I
like to create a Keycloak on Openshift using the Keycloak cartridge and then
automatically populate its realm. Should I kill the startup in the action
hook? It seems a little strange.
Thx.
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user