On Tue, Mar 30, 2010 at 9:09 AM, Roy Nielsen <r...@lanl.gov> wrote: > On 3/30/10 9:33 AM, Nigel Kersten wrote: >> >> On Tue, Mar 30, 2010 at 8:21 AM, Roy Nielsen<r...@lanl.gov> wrote: >> >>> >>> On 3/30/10 8:49 AM, Thomas Bellman wrote: >>> >>>> >>>> JeFFreaK wrote: >>>> >>>> >>>>> >>>>> i'm stuck with the plugin in modules section. >>>>> i've got 2 environments set called >>>>> development and production. >>>>> >>>> >>>> [...] >>>> >>>>> >>>>> now i wanted to have the sysctl plugin inserted in my development >>>>> environment without harming anything in production. >>>>> http://github.com/duritong/puppet-sysctl >>>>> >>>> >>>> Unfortunately, not possible. There is some hope that this will >>>> work at least a little bit better in Puppet 0.26 (or whatever it >>>> will be called), but currently you are out of luck. >>>> >>> >>> This isn't quite the same - we have a custom package provider (as test to >>> show we could do it) - what we're doing is specifying different >>> "modulepath" >>> for each environment in the server's puppet.conf file. >>> >>> To make it work we had to put the provider in our puppetmaster's >>> $libdir/puppet/provider/package directory, as well as the right place in >>> the >>> module.. >>> >>> That seems to be working for us. >>> >>> We haven't tried creating a separate type though.. >>> >>>> >>>> For custom types and custom functions, puppetmasterd will only >>>> look at the *global* value of modulepath, i.e the one you have >>>> set under [puppetmasterd] or under [main]. The modulepath you >>>> have set under each environment will not be used for those. You >>>> didn't have a global modulepath setting at all in puppet.conf; >>>> you need to add one to get plugins in modules to work *at*all*. >>>> >>> >>> So it doesn't look at "modulepath" under an environment definition in the >>> puppet.conf on the pupetmaster? >>> >> >> It does for *delivering* to clients, but for validating the manifests >> in order to turn them into a catalog, it looks at the local libdir for >> the puppetmaster. >> >> As Thomas says in the next message that just arrived, functions are >> different as they execute on the server, and types are different due >> to parameter validation being employed. >> >> The problem I reported on puppet-dev with providers being pulled in is >> only if you're setting global resource defaults in your manifests. >> > > ahh.. ok. Thanks,
This is all quite horrific to grok conceptually, and I'm not pretending otherwise by the way. The completely reasonable expectation is that functions, types and providers are completely self-contained within an environment, but that's not the case. -- nigel -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
