Hi Mark, Yes, it's possible. You can add a new path in etc/config.properties in felix.fileinstall.dir. You can also add your own property (like karaf.etc.my) or use explicit path in your feature.
Regards JB On Thu, Aug 25, 2022 at 8:52 AM Mark Derricutt <[email protected]> wrote: > > Hey all, > > Is it possible to run Karaf with multiple configuration paths? > > I’m trying to build up a custom karaf distro to build into a docker image, > and want to keep all our apps service config separate ( to be injected via a > docker volume or something ) whilst maintaining any generated > startup.properties or other system configuration files that get added. > > Alternative to that, I see in > https://karaf.apache.org/manual/latest/provisioning - I can pull in config: > > <configfile finalname="${karaf.etc}/myfile.cfg" > override="false">URL</configfile> > > > which I suspect that might actually do the trick - specifying the path of > whatever volume mount I’m using, if reading this correct I’d use it like: > > <configfile finalname="${karaf.etc}/myfile.cfg" override="false"> > file:///docker/binded/here/myfile.cfg > </configfile> > > > and remove the version I’d normally store in ${karaf.etc}. One thing that’s > not mentioned in the provisioning doc is what happens when that URL doesn’t > resolve, or cannot be downloaded for whatever reason - is that a silent > failure or does it stop the feature from being started? > > Mark > > > -- > "Great artists are extremely selfish and arrogant things" — Steven Wilson, > Porcupine Tree
