Hi JB,
jbonofre wrote > 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. The way I am using it: My bundle contains a blueprint context file with <cm:property-placeholder persistent-id="pep" update-strategy="reload" /> One of the property values in pep.cfg is a password. In development I want the password to be picked up from the pep.cfg file. In production I would like to leave the property out and have the operations team enter it on the Karaf shell via the config admin. Without the property and the value ever being persisted anywhere. So, ideally there would be a way to declare single properties as "transient". From what I read this is not possible but setting felix.fileinstall.enableConfigSave = false should prevent any change made via the config admin from being persisted. At least that is how I read the documentation. Thanks! Ralf -- View this message in context: http://karaf.922171.n3.nabble.com/felix-fileinstall-enableConfigSave-false-ignored-tp4047867p4047869.html Sent from the Karaf - User mailing list archive at Nabble.com.
