Hey James,
Your solution for using ANSIBLE_ROLES_PATH works! I am having issues trying
to find out where the *constants.py* file is that you're talking about.
On Tuesday, February 10, 2015 at 8:57:17 AM UTC-5, James Cammarata wrote:
>
> No problem. By design, every configuration option has a
No problem. By design, every configuration option has a corresponding
environment variable you can use, just look in constants.py to see them
(they all start with ANSIBLE_).
On Tue, Feb 10, 2015 at 6:29 AM, Tom Bamford t...@atpla.net wrote:
Thanks James, I didn't know about this. Will come in
Thanks James, I didn't know about this. Will come in very handy!
On 10 February 2015 at 08:27, James Cammarata jcammar...@ansible.com
wrote:
Hi Daniel, you can use the environment variable
ANSIBLE_ROLES_PATH=/path/to/roles in front of ansible-playbook to modify
the path on the fly, without
Hi Daniel, you can use the environment variable
ANSIBLE_ROLES_PATH=/path/to/roles in front of ansible-playbook to modify
the path on the fly, without having to modify your ansible.cfg (or deploy a
local cfg in the working directory). In either case, the roles path can be
a colon-separated list
Aha! That's perfect - thanks James
--
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
Is it possible to pass the roles_path parameter (from ansible.cfg) or an
equivalent as an argument to ansible-playbook?
My use case is: I'm using the ansible-galaxy (tool not web service) to pull
my shared ansible roles from private GitHub repositories into a local
directory called
