Re: [ansible-project] Re: How do I use multiple ansible versions on the same machine for different playbooks that require specific versions?

I would also suggest python virtual environments. Although, I have also used Docker images for running Ansible. I create a Docker image with 'ansible' as the ENTRYPOINT, then create a shell script to execute 'docker run -it --rm []'. This will execute ansible inside the docker and use the

Re: [ansible-project] Re: How do I use multiple ansible versions on the same machine for different playbooks that require specific versions?

2016-07-28 19:57 GMT-04:00 Subramanian P V : > I am facing the same situation. Is there a way to run ansible like an > excutable like sourcing in old environments. I have a setup where ansible > 1.5 is present and on the same machine i need to execute the ansible >

[ansible-project] Re: How do I use multiple ansible versions on the same machine for different playbooks that require specific versions?

Hi Philip, I am facing the same situation. Is there a way to run ansible like an excutable like sourcing in old environments. I have a setup where ansible 1.5 is present and on the same machine i need to execute the ansible scripts of 2.0.0.2 version Thanks Regards Subramanian On Wednesday,

[ansible-project] Re: How do I use multiple ansible versions on the same machine for different playbooks that require specific versions?

I would propose you to use python's virtualenvs: virtualenv ansible17 source ansible17/bin/activate pip install ansible==1.7 # work with it deactivate # next time source ansible17/bin/activate It is the same approach as you are using, but as virtualenv encapsulates the whole environment, so

[ansible-project] Re: How do I use multiple ansible versions on the same machine for different playbooks that require specific versions?

I would propose you to use python's virtualenvs: virtualenv ansible17 source ansible17/bin/activate pip install ansible==1.7 # work with it deactivate # next time source ansible17/bin/activate It is the same approach as you are using, but as virtualenv encapsulates the whole environment, so