On 05/24/2011 12:29 PM, Jonathan Gazeley wrote: >> If you manage to deploy an utterly broken config, puppet won't be able >> to get itself back up to speed because it cannot start anymore. >> >> Am I missing something here? > > No, you are correct. If I deploy a garbage config, it will break the > puppet clients. But the benefit is that I can easily deploy a modified > puppet config to many clients if we need to add extra config parameters > in future. > > I can mitigate the risk by carefully testing the new puppet.conf on an > isolated dev machine.
That's an utter relief. I've deployed a mechanism that will deploy a puppet.conf alongside the actual one and notify a script that becomes active after the catalog run proper. It activates the new config, but if puppet is found to not run correctly afterwards, the original config is restored instead. Cheers, Felix -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
