James Turnbull wrote: > 2009/11/17 Scott Smith <sc...@ohlol.net>: >> Has anyone given thought to the best way to maintain multiple versions >> of a manifest in a way that allows a client to specify which version it >> would like to use? I actually thought that's what config_version was for >> until I read the docs...boo hoo. >> >> Seems like it would take some hacking. I think it would be nice though, >> giving more control over when a client would get a newly pushed manifest >> while allowing puppetd to continue running (instead of using puppet >> command directly with no client daemon). > > I use tags and environments for this: > > http://reductivelabs.com/trac/puppet/wiki/UsingTags > http://reductivelabs.com/trac/puppet/wiki/UsingMultipleEnvironments >
Yeah, I considered environments. I'd just rather not have to change my puppetmasters' puppet.conf when I want to deploy a new manifest version to them. It wouldn't be *difficult*; I'm just concerned with the puppet.conf becoming unwieldy after a while. > Also being added in the next major release - currently code-named > Rowlf - is module metadata. You can see the proposed code at: > > http://github.com/lak/puppet/commit/3896288ff56b44ae6f5e1f0c2a8adc995a458f76 > > This is just an initial cut but should let you see what could be done. > Hmm, interesting. Thanks, Ohad & James! -scott --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
