Morning all As part of my work to create an Apache Karaf module[1] I need to manage a number of configuration files, and I'm wondering what the best way to go about it might be... A couple of examples of the config files that need managing can be found here[2]. I think the 2 provided examples give different challenges. *jre.properties*[3] strikes me as the most troublesome initially, due to the nature of the contents and the format reqs... My initial thought is to provide a type that can manage the file, and possibly use Augeas to manage the file. Happy for other suggestions though :) *wrapper.conf*[4] looks like it should be fairly easy to template. The only thing I'm not sure on is how to handle the incrementing nature of the param lines... I'd like to keep the number of resource params as light as possible, as there's no way I can expose all the possible config lines, so I'm thinking maybe use an array for each 'set' of config lines, e.g. 'wrapper.java.classpath' and 'wrapper.java.additional'... But then how do I handle over-riding pre-existing config values? Is there a better way to handle this file? Thanks in advance for any suggestion... Regards Gavin [1] https://groups.google.com/forum/#!searchin/puppet-users/karaf/puppet-users/dcV6Qt480cE/F_Yhj5XsJogJ [2] https://gist.github.com/fatmcgav/684803f83e3b15118e79 [3] https://gist.github.com/fatmcgav/684803f83e3b15118e79#file-jre-properties [4] https://gist.github.com/fatmcgav/684803f83e3b15118e79#file-wrapper-conf -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/13063245-577f-4b21-8546-6d307fdd6115%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.