On Nov 8, 2010, at 2:03 PM, Richard Crowley wrote: >>> +1. Catalogs that need to "converge" or are anything but a no-op on >>> their second run should be considered broken. >> >> *) My philosophy is this puppet.conf should be managed by puppet. >> *) Sometimes a run won't be completed correctly unless puppet.conf is up to >> date at the start of a run. >> >> Which of these do you disagree with?
> On agents, /etc/puppet/puppet.conf is written by a > bootstrap.sh program when the server comes up for the first time. > > My puppet.conf is only 5 lines long and has never changed. I may be > in the extreme minority here. I used to do this, but then I wanted to turn on reporting on the clients and at that point I started pushing out puppet's config so that I wouldn't need to change puppet.conf on each computer individually. Later I changed it again to turn on pluginsync. By that time I got tired of managing puppet.conf in two places so I just manage it using puppet now. Why would you use Capistrano to manage puppet.conf on your masters? Does it give you some advantage over just using puppet to manage itself? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
