Issue #2624 has been updated by Ken Coar.
In addition, plugins namespaced this way should **not** have collision issues with any 'global' list of plugins. I have encountered problems with a module being imported to our Puppet environment which had a private parser function with the same name as one of the global ones already in use. The module-specific one replaced the global one on sync, screwing things up. Or should that be a separate issue? ---------------------------------------- Feature #2624: custom parser functions should be namespace-able https://projects.puppetlabs.com/issues/2624#change-82048 Author: Jordan Sissel Status: Accepted Priority: Normal Assignee: Category: functions Target version: Affected Puppet version: 0.24.8 Keywords: Branch: If I define a function in module/foo/plugins/puppet/parser/bar.rb, and call it 'bar', I want to be able to access the function in puppet manifests as 'foo::bar'. Current documentation recommends putting plugins/functions/etc in modules, so it makes sense to be able to reference those functions by module namespace. Currently calling a function as foo::bar() results in a syntax error. -- 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]. Visit this group at http://groups.google.com/group/puppet-bugs?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
