Issue #7788 has been updated by Chris Price.
We need to do some profiling around the autoloader and how performance changes as the number of paths grows, but the more I think about this set of issues (see also #7316 and this pull request: https://github.com/puppetlabs/puppet/pull/882 ), the more I agree with this being necessary. ---------------------------------------- Feature #7788: Puppet should allow rubygems to deliver new functionality https://projects.puppetlabs.com/issues/7788#change-65746 Author: R.I. Pienaar Status: In Topic Branch Pending Review Priority: Normal Assignee: Kelsey Hightower Category: plug-ins Target version: 3.0.0 Affected Puppet version: Keywords: rubygems autoloader Branch: https://github.com/puppetlabs/puppet/pull/873 It would be desirable to use Rubygems to install things like parser functions. There might be cases where you only want a function on the master, pluginsync would copy it everywhere and everywhere might not have the dependencies needed to run it. If the autoloader considered the rubygem search path while autoloading this should allow gems to extend puppet. Update: Just to be clear, this ticket is about whether Puppet should allow rubygems as a delivery mechanism for Puppet extensions like parser functions, Faces, types and more. If added in, you could deliver Puppet extensions via modules with pluginsync and via installing a Ruby gem. Both the Puppet DSL and Puppet's Ruby DSL would be untouched. -- 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.
