On Tuesday, September 30, 2014 7:17:51 PM UTC-4, Tom Tucker wrote: > > > I just got back from PuppetConf last week and several presenters mentioned > using more than one Git repo with Puppet. Some even recommend having a > repo per module. For our initial Puppet deployment this seems a bit > excessive. My plan was to have three repos for each of our environments > (Dev, QA and Production). The contents of these repos would contain Puppet > Enterprise directory of /etc/puppetlabs/puppet. > I'll echo what other people have said here about single repo vs multiple repo. You might be fine with a single repo if you have pretty basic configurations, but it has definite limits.
One thing I'd *strongly* recommend against is having different repositories for different environments. Assuming you're using Git, you should at most have these be separate branches in the same repository. Longer term, you may want to move to using tags and (maybe) release branches for QA and Prod environments. Having 3 branches will give you a lot more tools for moving changes between branches and for comparing differences between them. Personally I think this is a lot more important than all modules in one repo vs a repo per module. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/496a0d42-999a-4d42-915c-3eb95b3e7f16%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
