Jira (PUP-3482) server-side only execution stub

[Andy Parker (JIRA)]

Title: Message Title

Andy Parker commented on an issue   Re: server-side only execution stub Would puppet-server still implement Puppet::Util::Execution.execute? If not then there are some modules that would end up breaking, one of them being stdlib because of the validate_cmd function. We've never had a distinction before between "client" and "server" API, but maybe we've hit the point were that distinction needs to be made. One consequence of that is that the "server" APIs will, in general, also need an implementation to run on a "client" system because of puppet apply. Maybe that is what makes a "server" API public is that it will need a non-puppet-server implementation. Another solution to this is to stop using the Puppet::Configurer for the settings catalog. It doesn't need to pre and post run commands. It doesn't need to send a report. It doesn't need the last_run_summary. However, I realize that it doesn't technically solve the problem since there are still going to be functions and ERBs that can call Puppet::Util::Execution. Add Comment   Puppet / PUP-3482 server-side only execution stub In puppet-server, we install an 'execution stub' into puppet. The reason for this is that, when no execution stub has been installed, {{Puppet::Util::Execution.execute}} eventually ends up calling {{Kernel.fork}} to run the command, and {{Kernel.fork}} is not available on JRuby. {{Puppet::Util::Execution.execute}} takes a second parameter which is a s... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.