It's not uncommon to run a small staging environment for just this purpose. Have you evaluated something like that and found it wanting?
On Fri, Mar 2, 2012 at 7:26 PM, Ryan Bowlby <[email protected]> wrote: > Hi All, > > We'd like to do some form of testing of our module changes against > production nodes before being released into production. While somewhat > expensive it seems doing a noop against all nodes using the modified > module is the best way to determine unexpected results. > > The question then is how are people implementing this? Any real world > talks or posts describing something like this would be great. Ideally > we want to put a git pre-push hook in place within the production > branch that performs a noop catalog run against the affected nodes and > reports results and determines if errors were encountered. > > Thanks!!! > Ryan Bowlby > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > -- Brian L. Troutwine -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
