Issue #6865 has been updated by Mohamed Lrhazi.
By "problematic" I was simply thinking in terms of mcollective expecting commands to finish in under the default 3 seconds timeout. I kind of forgo about other implications.... Ok.. How about a config parameter that the user can use to set exactly what options are allowed? "allowed_options", which would default to what we consider to be safe, maybe just "noop" "no-noop", and then leave it up to the user to decide beyond that what risks they are willing to take? ---------------------------------------- Feature #6865: Proposed patch to add support to puppetd agent extra command line args https://projects.puppetlabs.com/issues/6865 Author: Mohamed Lrhazi Status: Needs Decision Priority: Normal Assignee: R.I. Pienaar Category: Target version: Keywords: Branch: Affected mCollective version: I am suggesting a patch for puppetd agent, which allows the user to pass arbitrary command line arguments to be passed to puppetd. Please the forked here, branch name: puppetd_options https://github.com/lrhazi/mcollective-plugins Thanks. -- 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.
