I was thinking exactly the same as Eric. It seems like we're repeating what Git does.
Trevor On Tue, Jul 7, 2015 at 12:34 PM, Eric Sorenson <eric.soren...@puppetlabs.com > wrote: > On Mon, 6 Jul 2015, John Bollinger wrote: > > 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. >> > > Is that really the domain of the compiler/catalog cache, though? Seems > more like the purview of the code testing and promotion workflow, because > it requires a test/feedback/fix interaction loop, not an on/off flag. > > Eric Sorenson - eric.soren...@puppetlabs.com - freenode #puppet: eric0 > puppet platform // coffee // techno // bicycles > -- Trevor Vaughan Vice President, Onyx Point, Inc (410) 541-6699 -- This account not approved for unencrypted proprietary information -- -- 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/CANs%2BFoWc%3DKd5i9LL4e3EQEDa%2BLZ2qpeHG7Axb46JRch6UkCpqw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
