Lumenvox services write over their config files

[JustinAiken]

The endless cycle

All of the various services tend to write their own config files, based on what's there and the version... right now this causes an endless cycle:

1. A puppet run is started
2. Puppet sees the config file has changed, so it installs it's own from the template
3. The service resource restarts because it sees the config file changes
4. Upon restarting, the service sees that it's config file has changed, and overwrites it
5. GOTO 1

Impact

The service keeps all the values in the config file the same, so no great harm is done, but it causes runs that should write no changes to have 4 or 5 changes everytime.

Solution?

I think the only way to fix this will be to move away from managing the config files as a file resource from a template source, and instead set individual values in the config file using file_line instead.

[benlangfeld]

Why does Lumenvox write config files on service start? That’s broken.