-
Notifications
You must be signed in to change notification settings - Fork 2
Make OBP-Keycloak-Provider fully configurable via ENV variables #2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
- Resolved merge conflicts in .gitignore - Combined environment variable support with upstream CI/CD improvements - Kept persistence.xml with environment variable placeholders - Added comprehensive environment configuration tooling
- persistence.xml should be generated from persistence.xml-example - Contains environment-specific configuration that shouldn't be in VCS - Already listed in .gitignore but was previously tracked
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While this approach technically works, it does not support k8s deployments or deployments from e.g. a Dockerhub-hosted image.
The run-with-env.sh builds a customised image injecting the env vars to maven, but we rather need to be able to configure the keycloak provider via env vars at run time, not at build time.
So the java artifact needs to be able to read the env vars when it boots.
In general, custom shell scripts to build and run a container don't work with Kubernetes. And we want to be able to host generic and ready-to-use docker images on Dockerhub in our standard deployment pipelines.
cloud-native deployments with runtime configuration
Keycloak Admin Console
persistant fast integer `id`
code and docmentation
been configured as READ-ONLY
No description provided.