Below - didn't mean to toppost last time.
On 08/16/2012 10:46 AM, Dan White wrote:
May I politely disagree ?
I feel that using subversion branches for the different environments
is defeating the fact that Puppet separates the environments thru the
use of the environment setting.
Does that make any sense to you all ?
“Sometimes I think the surest sign that intelligent life exists
elsewhere in the universe is that none of it has tried to contact us.”
Bill Waterson (Calvin & Hobbes)
------------------------------------------------------------------------
*From: *"Jason Slagle" <raist...@tacorp.net>
*To: *puppet-users@googlegroups.com
*Sent: *Thursday, August 16, 2012 9:28:29 AM
*Subject: *Re: [Puppet Users] Managing puppet code
Although it doesn't seem to do svn yet (You could extend it), I'm fairly
certain you could accomplish this with librarian-puppet.
It's on github.
Your Puppetfile would be in your main repo which could have
dev/stage/prod branches.
I suppose it depends on your use case. Some people use environments for
testing puppet, some people run seperate puppetmasters etc to do so.
Having attempted to manage this with git submodules and environments in
the past, it's a real pain to make sure things happen the way you want
them to. Throw subversion into the mix and this is a real issue.
Manually promoting code from the "dev" enivronment directory to the
"production" directory is a non-starter for most people, so at best
you're going to see people check out seperate branches for each
environment, which is still a branch model. I still believe you could
manage this with librarian-puppet - just do a puppetfile in each of the
enviornment dirs.
Jason
--
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.
