Actually I was already thinking of spliting _modify_module, for one, it should not need/handle/know about become_kwargs and we should eliminate the passing of these, which is kind of the opposite direction of your proposal.
As for action plugins, they already do too much and have too much information for their needs, we are looking at moving these things into a more generic/changeable 'executor' that should handle those parts and leave the 'action plugin' to just coordinate local and remote actions w/o having to deal with the details as they do now. -- 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 ansible-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-devel/905081cc-ea59-4574-aabe-0d21d38a22efn%40googlegroups.com.
