Repository navigation
Replies: 1 comment 5 replies
|
This is currently not possible with the Quarkus Keycloak deployment. You need a keycloak server (or at least keycloak cluster node) restart for reloading providers/extensions.
|
|
Is this still the case? |
|
Does this mean that if I deploy a custom theme as a jar, there is no way around a server restart if I want to be able to activate that theme? |
|
Try running in quarkus dev mode: https://github.com/keycloak/keycloak/blob/main/quarkus/CONTRIBUTING.md#running-the-server-in-development-mode I believe that changes to existing provider jars are picked up, but new jars aren't yet handled - I haven't tested this in a while though, so it may work now. |
Thanks for the reply. I don't know whether changes to an existing jar are picked up on the fly, but hot load of new jars does NOT work, even if dev mode is enabled. |
|
This feature would be appreciated |
Uh oh!
There was an error while loading. Please reload this page.
Hi,
After the migration to Quarkus, is there a way of using Quarkus' Dev Services with Live Reload when doing development of custom Keycloak extensions?
If anyone has a good write-up on a good dev workflow including both live/low friction reload, it would be highly appreciated.
All reactions