Issue #7788 has been updated by Ashley Penney.
+1 from me after quizzing #puppet about what benefits this brings. My main
concerns lie around the examples from above. If I have a manifest that uses
hiera and also has a package { 'hiera-puppet': provider => gem } will it be
smart enough to load up the gem dependencies and run the catalog? I just don't
want a situation where I need a third party tool to install various gem's just
to get a puppet run functioning. As long as that isn't a problem or can be
worked around then this sounds great.
----------------------------------------
Feature #7788: Puppet should allow rubygems to deliver new functionality
https://projects.puppetlabs.com/issues/7788#change-65660
Author: R.I. Pienaar
Status: In Topic Branch Pending Review
Priority: Normal
Assignee: Nigel Kersten
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.
--
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.
