On Thu, Feb 23, 2012 at 11:09 PM, jimbob palmer <[email protected]>wrote:
> I'm worried about making bad changes to a module which will impact > lots of hosts. > > How can I avoid this? > > Ideally I'd like every node to run in noop, and then to approve the > changes if they look right. > Hi Jim, We're not currently using this method, but we're planning on using a second Puppet server which will have a copy of the Puppet tree with whatever major changes have been made in development. We run Puppet from cron so every host would continue to point at the master server, but we would connect to specific hosts and try noop against the second Puppet server. I'd like to hear how other people manage this sort of thing. - Gonzalo -- 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.
