duh, right. It works for connection: local, but not for remote targets. Maybe have a task that copies it to a tmp dir on the target and then append that to sys.path in your module?
On Wednesday, March 23, 2016 at 7:43:19 AM UTC-4, Uditha Desilva wrote: > > Does that really work to copy over the dependent libraries to the target > systems? > > On Tuesday, 22 March 2016 17:13:38 UTC, Mike Biancaniello wrote: >> >> You can put them in the same or sub dir as your modules. Or, you can put >> them anywhere, just append the path in the module. However, if you want >> multiple modules in multiple roles to share the same libs, then things get >> tricky. I've done that by appending '../../pylibs/' to my sys.path to get >> things up and running, but eventually just installed the libs globally on >> the system and did away with that ugliness. Of course, you could always >> just run ansible inside of a docker or python-virtualenv and then install >> the libs local to that environment. >> > -- 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 post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/fcf7dc96-4f16-411e-bbcf-d18d15486c69%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
