Issue #6865 has been updated by Mohamed Lrhazi.
am not sure I understand. Are you saying you would be willing to accept --options, if it came with an "allowed_options" config setting? or you would rather see two additional boolean options only, --noop and no-noop? In our site, I'd say that we cannot live without noop/no-noop, and would be happy to have the option of additional "options" if we ever needed them someday: --server/--tags/--environment... mcollective can affect systems that are unreachable via SSH, say due to LDAP issue, like we had recently after some ssl certs were updated on the LDAP servers... so it could act as an "out-of-band" path to access and fix some problem that would otherwise require console access to each and every system... So, there might be cases where the ability to run puppetd in an "unexpected" way, might be useful. Thanks a lot. ---------------------------------------- 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.
