Issue #13858 has been updated by Jeff McCune.
Pall Valmundsson wrote: > How about a backport to the 2.7 series? Is the 2.7 also in > critical-security-fix-only support? We don't have any plans to backport this to Puppet 2.7 either, there have been enough changes between 2.7 and 3.0 related to plugins and code loading that it would be quite an undertaking to support this fix across the two major versions. Are there issues blocking you from upgrading to Puppet 3.0? ---------------------------------------- Bug #13858: Custom types in environments require loading into master's libdir https://projects.puppetlabs.com/issues/13858#change-77526 Author: eric sorenson Status: Closed Priority: Normal Assignee: Patrick Carlisle Category: modules Target version: 3.0.0 Affected Puppet version: Keywords: Branch: https://github.com/pcarlisle/puppet/tree/ticket/master/13858-types-in-environments An attempt to distill down the back-and-forth from #4409, as it applies to 2.7.x: * The master needs to load new types locally to validate parameters * In order to do so, the type rb files need to be available in the master's `$libdir`, and only get there by being pluginsync'ed * Therefore, environments which have custom types in `$modulepath` directories that the master does not itself use (when running as a client), cannot be used. -- 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.
