If I understand your question, the reason I don't just export to /etc/puppet is that the git repository contains files other than the puppet configuration, and I prefer to keep those files out of the puppet directory.
Certainly one could clone the bare repository in /var/lib/git, and symlink /etc/puppet to the puppet directory in that non-bare repository. Then the script that executes puppet apply would first run git pull, then puppet apply. I didn't do it that way for no reason other than I didn't think to do it that way. In fact it might be less complicated to implement, in exchange for some more disk space. Charles > On Mar 12, 2015, at 10:42 AM, hubert depesz lubaczewski <dep...@gmail.com> > wrote: > > I understand most of it, but why checkout as /etc/puppet_hash, and and not > simply as /etc/puppet, and just `git pull` when necessary? > > I.e. What is the benefit of having to do clone from scratch on every run > (i.e. when something has changed)? > > depesz > -- 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/190FCE9C-CD14-47C3-A338-D3ECEB13D6CB%40dakim.com. For more options, visit https://groups.google.com/d/optout.
