Issue #15427 has been updated by eric sorenson. Status changed from Unreviewed to Rejected Assignee set to eric sorenson
mcollective 2 allows point-to-point comms instead of broadcast. `puppet kick` will start deprecation cycle in telly so it's not going to get new features. (#15735) ---------------------------------------- Feature #15427: Ability to force application of arbitrary manifest/module with puppet kick https://projects.puppetlabs.com/issues/15427#change-68929 Author: Ken Johnson Status: Rejected Priority: Normal Assignee: eric sorenson Category: Target version: Affected Puppet version: Keywords: Branch: A customer is interested in having the ability to use puppet kick to force the application of an arbitrary module or manifest to a host regardless of that node’s classification. You can use the --tags argument and target a tag (or implict tag by passing a class name), but this doesn't work if that class isn’t classified to the node in the first place. They are using puppet kick instead of mcollective since they want to avoid broadcasting to an entire collective. -- 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.
