Interesting. Nice discussion. I think one issue is that there would be no easy way to revert tasks that fail without some type of API that instrumented changes. Either that or have the tasks run in some sort of container that logged changes. But of course you're not sure what type of changes to expect. It could be a sysctl, FS changes, API call, etc. How do you reliably roll those back?
So I guess the solution is to just be careful and know what your scripts are doing. And maybe in the future tasks could implement a rollback API for when they fail but of course this might not be reliably supported everywhere. -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/30797ca0-8128-4f2e-9600-0650d1b92d40%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
