Daniel Baumann wrote:
old-school config handling requires manipulating one file,
e.g. /etc/ssh/ssh_config.
when doing configuration management, then that is very unfortunate
design (thus unrelated of the implementation of the configuration
management, be it homegrown or any of ansible/puppet/chef/$whatever...),
because the file has to be parsed and edited - which inevitably always
leads to problems over time, no matter how "good" the parser for a
specific conffile is (be it comments added, local changes, or just the
fact that the package management (dpkg/rpm) treat it as "modified" and
thus will prompt for it on upgrades).
the way to fix this completely is to allow to drop "snippets" of config
files into a directory, which then are read lexicographically sorted.
Thank you for the explanations. I had not heard about configuration
management before.
I guess I'm very "old-school", because I can't imagine zcmp implementing
something like this and wasting more time in assembling the config file than
in doing real work (comparing bytes).
Best regards,
Antonio.
