short answer to subject: no, callbacks cannot influence play flow As for your particular case i would argue that most modules are designed to prevent doing the same action x2 on the target machines, if using shell/command look at creates/removes checks on sideeffects. I don't think this is something you want to build into the controller but into each action as it is sometimes too hard for the controller to verify such things.
For example, if the task succeeds but then the update to your database fails, you will re-execute the task, while if the action itself verifies 'do i need to execute' by examining the expected state, you are always safe to run the play no matter what. What you are attempting to do goes against the design of Ansible itself and it's actions, so i expect it to be full of problems going forward. jic you still insist on this direction, here are some tips: possible solution: strategy plugin, these are the plugins designed to control play/task flow. other info: tasks already have a uuid but it is generated on task definition, which might mean you will see it more than one time, example: execute same role x2 (task definitions are the same). -- ---------- Brian Coca -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CACVha7eqq1zqnAx%2B_QPQPtHksrQ5By9BgcvVzbzJYB5xvuq-FA%40mail.gmail.com.
