> There are a bunch of workarounds for this though. > > A lot of the time you can get away with just a shell provider and type > for manifest validation, as the client will get the right one synced > down for use in actual resource application.
I thought I understood what you were suggesting, but apparently not. The default environment is "production" on my system, so I replicated my custom type in the "custom" module in the production environment. Still received the same error. I removed it completely from the "development" environment and switched the client to production. Same "Could not find resource type blah" error. A quick look in $libdir (/var/lib/puppet/lib) shows my custom types are there. The type in question and my puppet config: http://pastebin.ws/6t422 I'm quite perplexed. -Ben -- You received this message because you are subscribed to the Google Groups "Puppet Users" 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-users?hl=en.
