So far I've gone the route of having two static environments, "production" (which seems to be the default) and "development". I had my own $environment definition which was overriding puppet's definition of $environment that caused some problems for a little while, but I've got that all sorted out, and now by changing my database (which in turn changes the results in the puppet node classifier) I can easily flip back and forth between the production and development environments. Very slick!
If I wind up playing with your dynamic creation of puppet.conf, I'll let you know how it goes. Thanks again for your pointer. Pete On Tue, Jul 7, 2009 at 8:45 AM, Pete Emerson <pemer...@gmail.com> wrote: > Brilliant! I think that will save me tremendously. I'll play with it and > let you know. Thanks very much. > > Pete > > > On Tue, Jul 7, 2009 at 8:22 AM, Ohad Levy <ohadl...@gmail.com> wrote: > >> >> Maybe this can save you some time... >> >> >> http://github.com/ohadlevy/puppet-multipuppetmaster/blob/582f98840e2c7bbea9d9e820a3060b09b0916306/templates/puppet.conf >> >> Cheers, >> Ohad >> >> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@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 -~----------~----~----~----~------~----~------~--~---
