[DOCUMENTATION]: missing documentation on how to load conf-file from other locations

[MonkeyCanCode]

With eclipse-link extension enabled, an end-user will be able to update polaris-server.yml to the following to use a persistent backend:

metaStoreManager:
    type: eclipse-link
    conf-file: xxx
    persistence-unit: xxx

However, this seems to be only able to read off files from META-INF dirs. As those dirs will get packed into the JAR, it is not ideal for prod deployment as well as source code check-in for version control. Is there any way for an end-user to set the conf-file location to other path instead (e.g. /etc/polaris/config/persistence.xml)?

[eric-maynard]

@MonkeyCanCode can you confirm if #79 addresses this issue for you?

[MonkeyCanCode]

@MonkeyCanCode can you confirm if #79 addresses this issue for you?

Hello,

This I tried locally couple days back after got the EclipseLink to work but later on this will fail on following line (u can try the same, it will failed on bootstrap as well):

emf = Persistence.createEntityManagerFactory(persistenceUnitName, properties);

This will raise error regarding unable to find persistence-unit (with FileStream, it does allows us to load file from other location but the above code will abort about not able to find persistenceUnitName. I am assuming this is specific to Jakarta. I am not very familiar with Java framework. Let me know if help is needed to test it again if you think this will work?

[aihuaxu]

@MonkeyCanCode There is a limitation that enforces the configuration to be in a jar. I made it to workaround in #88 to configure as as /tmp/conf.jar!/persistence.xml. Please take a look.

[MonkeyCanCode]

@MonkeyCanCode There is a limitation that enforces the configuration to be in a jar. I made it to workaround in #88 to configure as as /tmp/conf.jar!/persistence.xml. Please take a look.

Yes @aihuaxu, I took a look at that this morning. Seems to be a pretty odd limitation. However, it is usable for the time being. I can volume mount a config over then update the jar in pod to generate the new jar file with this external config. Thanks for the info. I will give that a try tomorrow.