On Wed, 10 Feb 2010, Michael DeHaan wrote: > We're attempting to provide a reason to not use cron :)
I have a requirement that puppet may not change anything on a production host without change control approval in advance. It would be nice if a new version of puppet had better support for this use case. Of course there are change control procedures for getting the manifests updated on the puppetmaster, but that's not enough; it's also necessary to run the puppet client only when specifically authorised. For example, the manifest update and a --noop mode client puppet run might happen during working hours, but the --no-noop client puppet run might happen during a maintenance window after hours. As far as I am aware, the existing combination of "puppetd --listen" on each client, and "puppetrun" on a central server, does not handle this use case, so I run "puppetd --onetime --noop" or "puppetd --onetime --no-noop" via ssh. --apb (Alan Barrett) -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
