Ok I got it working with system properties and it is indeed much simpler to
test (
https://github.com/Opa-/keycloak/commit/0fce88947c99c2077827c2ca52514edc7...
)
However it is not clear to me how will I inject system properties when
running Keycloak inside the official docker container.
Do you know if I need to override the entrypoint and add some arguments ?
From what I can see everything given in argument to the
*docker-entrypoint.sh* will be passed to *standalone.sh* script and will
end up being passed to the java command with *$SERVER_OPTS* variable.
Is that correct or is there a simpler solution ?
Best regards
On Tue, Sep 17, 2019 at 11:15 AM Stian Thorgersen <sthorger(a)redhat.com>
wrote:
A simpler option may just be to allow system properties as that would
be
much simpler to test.
On Tue, 17 Sep 2019 at 10:45, Vincent Letarouilly <
vincent.letarouilly(a)gmail.com> wrote:
> Hello everyone,
>
> I started some development on a closed ticket (
>
https://issues.jboss.org/browse/KEYCLOAK-6990) in order to add the
> ability
> to load environment variables through theme.properties for custom themes.
> I'd need some feedback from you to see if I'm taking the right path here
> as
> this is my first Keycloak dev and I'm not an expert in Java nor Maven.
> This is what I've done so far
>
>
https://github.com/Opa-/keycloak/commit/8f0517d17bd350d22d082516884a75788...
> but
> I'm quite unhappy with the duplication of the maven-surefire-plugin (you
> can see that on top of my plugin block, there's an existing
> maven-surefire-plugin plugin block) but I did not found other way to bring
> an environment variable into the test context.
> If someone could give me some feedback here it'd be very much appreciated
> :)
>
> Regards,
> Vincent
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/keycloak-dev
>