> Interactive transactions: > https://github.com/lak/puppet/tree/prototype/master/interactive_transactions > > This provides a simple prompt before changing any resource in a transaction, > with the idea being that you could give people like developers some control > over how Puppet ran on their system without just giving them carte blanche. > You have a few options: > > Change: Make the change > Noop: Run it in noop mode > Fail: Throw an exception, thus skipping it and all of its dependencies > Hold: Run this in noop mode in this and any later transactions > > That last option involved me building a simple system for storing the list of > held resources. You could use it to hold and release resources independent > of this interactive transaction (I unfortunately could not use the 'resource' > face for this, because it's already used for indirector stuff): > > $ puppet held_resources hold 'File[/tmp/foo]' > $ puppet held_resources list > $ puppet held_resources release 'File[/tmp/foo]' > > For this to make it into the system, we'd need a new event type, so that the > reports retained the difference between a held resource and a resource in > noop mode, and we'd need to think a bit about things like whether a held > resource should hold its dependencies, too.
I like this one as well Luke ... I could see this kind of thing going into core - its worth keeping our ears and eyes open for real-world case that this would solve I think. I believe its something that once it was in there, people would use it. ken. -- You received this message because you are subscribed to the Google Groups "Puppet Developers" 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-dev?hl=en.
