On Mon, Apr 20, 2009 at 6:11 PM, Jason Rojas <[email protected]> wrote: > > With the use of the > [production] > and > [development] sections of the puppetmaster config, you can specify a > plugin path, you can have it either be shared, or the same directory just > checked out from the development branch in subversion, in my case it is: > > [production] > pluginpath=/opt/puppet/production/plugins > [development] > pluginpath=/opt/puppet/development/plugins > > both the directories production and development are different branches in > my svn repo.
Have you tested this Jason? This certainly never used to work... You'd always get the plugins from the default environment no matter what pluginpath specified.... /me runs off to test again. > > -Jason > > >> >> So I'm curious... who is distributing plugins with a setup that uses >> environments? >> >> How do you do have it set up? >> >> A common plugins directory for all environments? >> Faking it out with a module called 'plugins' on a per-environment basis? >> Plugin distribution outside of Puppet with packages/etc ? >> >> >> >> -- >> Nigel Kersten >> [email protected] >> System Administrator >> Google, Inc. >> >> > >> >> > > > > > > -- Nigel Kersten [email protected] System Administrator Google, Inc. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
