On 20 August 2016 at 22:50, Chadwick Banning <chadwickbann...@gmail.com> wrote: > This is an issue I run into pretty regularly. If your Puppet infrastructure > is even moderately complex, I'd recommend NOT equating a Puppet environment > to an operational environment, operational environment being the groups of > machines known as dev, qa, staging, etc.
But how to you stage a roll out of an update. If you want it to go to dev then uat then prod ... or through some logical steps. presuming you have a common profile used by all. > > For instance, in my infrastructure we have 50+ different operational > environments. If I equate each one of these to a Puppet environment, I'd > need 50+ branches. While doable, this immediately becomes a nightmare if I > have a change that applies to all or some of the operational environments -- > say, changing something in my base profile. Now I have to a) hope all 50+ > branches are somewhat in sync, and b) merge my change into *each* branch 50+ > times. If the branches aren't in sync at all I very well might end up having > to fix unique conflicts each time I merge. > > This is *not* a place where you want to end up. Yes agree sounds like it would be a nightmare > [snip] -- 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/CAJ%2BQ1PXzQpq0J2gDMcGd2g6ugxn_E8VE0PjVDnHmP2COb%2BKdkQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
