On Friday, July 3, 2015 at 2:25:15 AM UTC-5, Chris Price wrote: > I have a question / thought experiment related to this, and would really > love to hear some feedback from the community: > > What would you think about a setup where your master never saw any of your > code changes at all, until you ran a specific command (e.g. 'puppet > deploy')? In other words, you hack away on the modules / manifests / hiera > data in your code tree as much as you like but your master keeps compiling > catalogs from the 'last known good' setup, until you run this 'deploy' > command? At that point, all of your current code becomes the new 'last > known good' and that is what your master compiles off of until you do > another deploy. >
I like that pretty well. If Puppet moved in this direction, though, then it would be nice to protect against "last known good" turning out to not be so good after all by making it a blessed configuration that has actually proven good. That way, if a fresh code deployment turns out to be bad then there is a genuine known good configuration that can quickly be restored. In other words, I'm suggesting three configurations instead of two: undeployed, deployed, and known good. John -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/2c25bdf8-e5e1-491a-a2e1-0ea86911ad0c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
