On Tue, Nov 19, 2013 at 12:25 PM, Bruce <bly...@yahoo.com> wrote: > Maybe. But usually I don't know I want this information, until I need it. > So having to turn on some debugging ahead of time doesn't help.
I am using etckeeper in conjunction with Puppet for exactly this use case. Additionally, my puppet configuration itself is under git. With those two things, it is trivial to walk back to any change. As etckeeper is not part of puppet, it tracks _any_ change on /etc, and this adds very valuable coverage. For example: if you install an rpm, and one of its dependencies installs a new cronjob (with some unexpected side-effect), Puppet will not give you visibility on that unexpected cronjob; etckeeper will. etckeeper is a keeper ;-) Aside: If puppet would replace its "file bucket" functionality with a git-based store I would be the happiest man on earth. The contents of files changed would be available by path as well as hash. git tags would also allow for a clean migration (preserving md5-based lookups for preexisting files). I am familiar with git internals -- I've authored parts of early git, and various importers still in use -- so I'd be glad to help flesh this out, if anyone is ever interested. Current file bucket is pretty useless to me in practice :-/ m -- martin.langh...@gmail.com - ask interesting questions - don't get distracted with shiny stuff - working code first ~ http://docs.moodle.org/en/User:Martin_Langhoff -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CACPiFC%2BEAQ2sDAvQAu1h%2BWUQUE_36vt%3DDiS76CE%2BWBQMDfcQCQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
