So async was handled by using a specific 'async' action plugin up to and including version 2.2, this precluded action plugins from being compatible with async (as this required a specific one)
In 2.3 we have changed how this works so it happens when you call execute_module, for the action plugin you just need to add a property `self._supports_async = True` and then deal with running the module with the async setting (see service/package for examples). As for the 'skip' module/action, there has been that feature request for a while, currently we only have the ability to 'fail' using that module or 'assert', a workaround is using a block with conditionals to apply to the 'rest of the tasks' in the play. ---------- Brian Coca -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
