Issue #4107 has been updated by Siim Põder.
Nigel Kersten wrote: > My intuition is that all options should pass through to the agent for the > duration of the run, but perhaps I'm missing some options that really only > make sense for the kick itself. > > Do any such options exist? At least passing --noop would be superawesome. Coupled with reports it would provide a nice deployment loop: puppetrun --noop <wait> parse reports -> no changes: great success -> changes: verify/acknowledge -> puppetrun ---------------------------------------- Bug #4107: puppet kick ignores --noop, and it isn't clear what the correct behavior should be https://projects.puppetlabs.com/issues/4107 Author: Jesse Wolfe Status: Needs More Information Priority: Low Assignee: Nigel Kersten Category: Target version: 2.7.x Affected Puppet version: 0.25.5 Keywords: Branch: puppet kick silently ignores --noop (and many other puppet configuration vars as well), but it isn't clear to me what the correct behavior of options to kick should be - should they affect the kick process or should they propagate to the remote machine for the duration of the run (see #864 and #3868)? -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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-bugs?hl=en.
