I am trying to run the route53 module locally, register its output and use 
that variable in a task for a remote host.

This works if i have boto installed globally, using connection: local. It 
does not work when using inside a virtualenv.

I reproduced this in a virtual machine with boto available globally, and it 
works. On my mac laptop, I am using boto/ansible inside a virtualenv and 
this is where boto can not be found for a remote host.

On my local machine, when running on a localhost (with python_interpreter 
set), it does work and boto is found, however the variable isn't available 
on the remote host.

On Friday, June 5, 2015 at 10:18:35 PM UTC-4, Brian Coca wrote:
>
> I don't think I'm parsing what you are saying correctly. I thought you 
> were running the task that required boto locally. 
>
> ansible_python_interpreter is what you use to direct ansible to the 
> correct python with the correct dependencies, it only applies for 
> those hosts for which you set it. 
>
>
>
>
> -- 
> 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 [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/2e717b79-589a-451b-a88f-6c2e14df13a8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to