Hi Reginald, Just a quick note, I'm not sure if you are aware of it, but the polaris.persistence.auto-bootstrap-types config property allows automatic bootstrapping. It defaults to in-memory storage only, but could be overridden for JDBC as well. A test example is in [1].
I hope this config is sufficient for most test and getting-started cases. It can be set as an env. var in docker or k8s. I'm not sure if our helm charts already provide a value for it, but it should be fairly straightforward to add one. Would that work for you? [1] https://github.com/apache/polaris/blob/fccc51ab111b7ee1a0d3c8898e94b0c54bc73d80/runtime/test-common/src/main/java/org/apache/polaris/test/commons/RelationalJdbcProfile.java#L28 Cheers, Dmitri. On Wed, Nov 19, 2025 at 1:14 PM Arsenault, Reginald P. <[email protected]> wrote: > UNCLASSIFIED / NON CLASSIFI? > > Hi, I'd like to re-open the topic of adding realm bootstrapping to the > Helm chart. I think it's a good idea to have to be able to quickly set up > polaris in one shot. It's possible to configure the bootstrap job so that > it runs only once upon install of the helm chart, that way you don't > bootstrap an already bootstrapped realm. There would be no way to configure > it so that you accidentally purge the realm, that could remain a manual > thing. What do you think? Are there any security concerns with that? Would > the potential to bootstrap an already bootstrapped realm make it not worth > it? > >
