If I understand you correctly, I think that would cause a lot of problems and trip-hazards for maintaining the existing cloud modules. Also, to expand on what bcoca said- you can't assume you're always running from the control host. *Most* people run the cloud modules under localhost / local_action, but there's nothing precluding you from running them on other hosts (and there are sometimes legitimate reasons to do so). The ansiballz module packager will almost certainly not do the right thing in the fallback case you're describing (again, assuming I understand what you're doing). Plus, I don't see how you could do it without touching the import logic in all the existing modules and running extra round-trips to the module exec host.
I don't think it's as simple as you make it out to be, and I suspect there are a lot of gotchas that would keep us from shipping it as a feature. That said, nothing stopping you if you want to take a stab at it. :) -Matt On Tuesday, November 1, 2016 at 5:48:45 PM UTC-7, Brian Coca wrote: > > The modules should not try to import from each other, since they can > execute on different machines than the one in which Ansible is installed. > > > ---------- > 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 ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/68b0d375-6036-4f38-83d9-632dd980f407%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
