Issue #15735 has been updated by Aleksey Zhukov.
Did I get it right, that the problem is not with `kick` but with `listener` part, and the problem is having a network server in a privileged process and exposing a whole `Puppet::Network::HTTP::WEBrickREST` just to serve the `run` indirection? Insecure, has some overhead but doesn't look like a terrible hack to me. Or there are other issues with that? As for MCollective - it has much worse overhead, mostly cognitive one - you have to grok it and deploy. A tiny DYI server that'd send HUP on authenticated request or maybe even a xinetd or, possibly, knockd could replace `kick`, without a hassle of having MCollective deployment just to trigger Puppet agents. ---------------------------------------- Bug #15735: Deprecate 'puppet kick' run mode https://projects.puppetlabs.com/issues/15735#change-101375 * Author: eric sorenson * Status: Re-opened * Priority: High * Assignee: eric sorenson * Category: agent * Target version: 3.x * Affected Puppet version: * Keywords: telly_deprecation * Branch: https://github.com/puppetlabs/puppet/pull/1129 ---------------------------------------- People interested in `puppet kick` functionality should set up mcollective. Supporting it causes problems like #10418. Let's consider removing it for Telly. -- 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
