so while you can specify a pluginpath for a specific environment, or you can simply create a module called 'plugins' for an environment that contains all the plugins in the files subdirectory, if I understand things correctly, we don't truly have separate plugins per environment.
We find we have to create a symlink in the puppetmasterd libpath to one of the plugin sources we're delivering, otherwise while the clients can retrieve the plugins, the server doesn't "know" about the types and the manifest compilation fails. This doesn't seem ideal, as it makes it difficult to use environments as a release process, given that you may have a completely different version of plugin 'foo' in: /path/to/an/environment/plugins/source/foo.rb /path/to/puppetmasterd/libpath/foo.rb which I assume will affect the compilation server side... Am I missing something here? Is it at all feasible to instead have the puppetmasterd add the environment plugin source to the load path before compilation and remove it afterwards rather than relying upon the local puppetmasterd libpath? Or have things changed so much in 0.25 that this isn't an issue? (I'll test out 0.25 today, but thought I'd fire this off first) -- Nigel Kersten [email protected] System Administrator Google, Inc. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Developers" 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-dev?hl=en -~----------~----~----~----~------~----~------~--~---
