Issue #4409 has been updated by Nigel Kersten.
There are a couple of reasons I think this is a high priority issue that deserves attention. * Setting a default modulepath is undesirable if you want undefined environments to simply fail rather than fall back to a default. * Having a single location for plugin lookup on the server is exceedingly problematic if you want a release process for plugins where the acceptable parameters for a type may change. * Usability. This seems to bite a fair few people when they're getting started with environments. ---------------------------------------- Bug #4409: puppetmasterd does not find custom types for environment http://projects.puppetlabs.com/issues/4409 Author: Rudy Gevaert Status: Investigating Priority: High Assignee: Category: Target version: Affected version: 2.6.0 Keywords: Branch: Hello, I can't get plugins in modules to work. I tried IRC and puppet-users (http://groups.google.com/group/puppet-users/browse_frm/thread/1fa5616448b1ffad) , all led to no help/solution :(. This is blocking me to deploy puppet in our infrastructure. err: Could not retrieve catalog from remote server: Error 400 on SERVER: Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid resource type vcsrepo at /etc/puppet/development/manifests/nodes.pp:37 on node puptest.ugent.be I have attached several attachments that show my config. thank you in advance -- 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.
