Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Import realm at startup
See original GitHub issueDescription
Similar to the Wildfly distribution, we should also allow importing a realm at startup like when using keycloak.import in Wildfly distribution.
IMO, we should not allow this in production but only when running the start-dev command and for development/testing purposes.
That said, perhaps we could have a --import-realm option.
Discussion
No response
Motivation
Improve developer experience by allowing importing realms at startup. Especially when running in a container.
Details
No response
Issue Analytics
- State:
- Created 2 years ago
- Reactions:4
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Really disappointed to see this wasn’t included in 17.0.1. It’s a requirement of our business, especially coming from older versions. Pre-baking realm into the images will have to do for now.
As concluded in duplicate discussion #10216, this is vital for production environments (i.e. for
start) in order to deploy preconfigured realms as end-users can not be expected to set up a realm matching the application’s needs. Using deployment descriptors for k8s/compose/openshift/… is basically the norm today and are expected to set up everything without needing admins to log into each service individually in order to integrate them. See also https://github.com/keycloak/keycloak/issues/10216#issuecomment-1042937867.