Hi,
it depends how you use it: Karaf is responsible of the config store via
ConfigRepositoryImpl:
https://github.com/apache/karaf/blob/master/config/src/main/java/org/apache/karaf/config/core/impl/ConfigRepositoryImpl.java
So, disableConfigSave may not help.
If you want to disable the Karaf part, you can use a "null" Storage.
Regards
JB
On 09/05/2016 03:50 PM, rsteppac2 wrote:
Hello,
For Karaf 4.0.6 I am trying to prevent changes made with the config:*
commands to be persisted by setting the property
felix.fileinstall.enableConfigSave = false
in Karaf's $KARAF_HOME/etc/config.properties. But it appears the setting
gets ignored. Whenever I issue a config:update the pending changes to the
edited configuration get persisted to its configuration file.
I found this thread
<http://karaf.922171.n3.nabble.com/Does-not-work-for-me-felix-fileinstall-enableConfigSave-false-td4042595.html>
, which did not make it through to the mailing list, reporting the same
issue.
This thread
<http://apache-felix.18485.x6.nabble.com/Bug-in-Fileinstall-felix-fileinstall-enableConfigSave-does-not-work-per-configuration-td4915996.html>
suggests I a might be overridden by another property
felix.fileinstall.disableConfigSave.
I tried to set the property and the true/false/none permutations of the two
properties just to be sure, but no setting disables the flush to the
configuration file.
The answer to this SO question
<https://stackoverflow.com/questions/38435784/apache-felix-file-install-example-in-karaf>
says about the enableConfigSave property:
"It enabled to save configurations back to files, if those configurations
contain the flag needed."
But I could not find other references to the mentioned flag.
Am I missing something?
Thanks!
Ralf
--
View this message in context:
http://karaf.922171.n3.nabble.com/felix-fileinstall-enableConfigSave-false-ignored-tp4047867.html
Sent from the Karaf - User mailing list archive at Nabble.com.
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
