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?
[snip...]
Regards,
-Roy
--
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.
