I've been happy with storing environment specific configuration in hiera. With hiera-eyaml, allows for different teams with different access to work from the same code base. Maybe not a single repo, but two: one for the project and the other for your hiera.
-Erik On Thursday, 16 April 2015 11:57:32 UTC-7, Alexander Dacre wrote: > > Looking for some guidance on how one would deploy Puppet with all > configuration and modules stored in Gitlab. > > There would be three environments - dev, test, prod - managed by four > teams. The idea is that each of the three environments configuration would > be managed by the respective team for application specific items, with an > IS team having the ability to manage all environments - for any global > configuration and support. > > I'm not sure if this is really a Git or Puppet question; possibly both? > > Any suggestions/advice would be appreciated. > > Thanks, > A > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/e425fa0c-017c-490f-a8f8-af25745c0ae3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
