Argh. But puppet client daemon will be running in the noop mode, so none of this will work. My bad.
On Fri, Sep 10, 2010 at 3:24 PM, mohit chawla <[email protected] > wrote: > Ugh, never mind the nick/name. > > So, one way I can think of doing is to put the puppet client's controlling > module, in a run stage that's executed before main, which will restart > puppet and toggle the noop value. > > On Fri, Sep 10, 2010 at 3:08 PM, mohit chawla < > [email protected]> wrote: > >> Any suggestions, folks ? >> >> On Wed, Sep 8, 2010 at 1:35 PM, alcy <[email protected]>wrote: >> >>> Hi, >>> >>> I wanted to have my puppet client daemons running in the noop=true >>> mode, and changes could be triggered centrally through puppetrun -- >>> noop false. Also it would be nice in an inverse situation, when client >>> daemons are running in the default (noop = false) mode and before >>> testing out a new(small,immediate?) module/feature/code, puppetrun >>> could be run with noop=true mode to test out the changes first. But >>> the noop option is not supported with puppetrun. So, before submitting >>> a possible feature request for 2.6.1 (there exists an old one, >>> http://projects.reductivelabs.com/issues/864) just wanted to have >>> thoughts of the community, whether they need this, are implementing in >>> a different manner, etc. >>> >>> -- >>> 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]<puppet-users%[email protected]> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/puppet-users?hl=en. >>> >>> >> > -- 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.
