Issue #3806 has been updated by Dan Bode.
after discussing this with Trevor, I think the only type of resource action that would need to be tracked are pending refresh actions. Everything else should be able to resolve correctly just with another puppet run. ---------------------------------------- Feature #3806: Atomic Puppet http://projects.puppetlabs.com/issues/3806 Author: Trevor Vaughan Status: Unreviewed Priority: Normal Assigned to: Category: Target version: Affected version: development Keywords: atomic transactions Branch: Per the mailing list: I thought I'd toss this idea out here to get pointed and laughed at before I Redmine'd it. I ran into the fun situation recently where I needed puppet to be more atomic. Basically: (A) Update file -> (B) Restart Service But...for some reason puppet got interrupted precisely between A and B! So, the next time puppet ran, my system wasn't in the state that I had described, instead the file had been updated but the service had not been triggered. This got me thinking about the concept of atomic puppet updates. It shouldn't be too difficult to write to disk/register the state of the operations as they happen and to be able to pick back up by default if a run is interrupted. I say this, of course, completely tongue-in-cheek as the last graph discussion I jumped into went on for tons of messages! -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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-bugs?hl=en.
