Is there a reason why Karaf is touching config files when loading them using 
cm:property-placeholder (Blueprint config)?

There are 2 issues with that:


1)      If using update-strategy="reload", if 2 bundles are loading the same 
config, they trigger their updates in infinite loop

2)      In docker container, I need to give explicite write permissions to user 
running karaf (in standard setup, using Openshift 'anyuid'  concept, a user 
running Karaf can read all files in container, but cannot modify them).

Best regards,
Lukasz Lech

Reply via email to