I understand the request, but the push is to separate those concerns as both from a security and simplicity perspective, action plugins should not be able or care about 'become settings', much less take part in manipulating module input.
Also note that while run_command is used by some modules, the vast majority use APIs instead of running commands, so become is more geared to running the modules themselves vs what the modules might shell out to do. So while what you ask for is not w/o reason, it is a niche use for a minority of modules and pushes against the desired design for most other use cases. ---------- 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 ansible-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-devel/CACVha7fR2MgBj_PdLyPF8GP%2BjoAfk1r01iSpr5wiBhNNEJ_zfg%40mail.gmail.com.
