no, play/roles/includes get compiled into a task list on the 'master',
once this is done each task is individually handled on the target
server, only the task code itself and arguments are copied to the
machine and then executed.
On Sat, Jun 6, 2015 at 1:06 PM, wrote:
> Thank you Brian for your
Thank you Brian for your explanation. I'm new to Ansible and don't
understand it perfectly. But it's better now. I use mainly Ansible in
the"pull" way, but it could be possible the other way round.
What I could do is to use the copy module to copy the Ansible role file
into a known temp file (/
as i mentioned above, modules execute on the 'target' host and cannot
access data on the 'master' themselves (the exception is when both
machines are the same, but it has no role/play context at this point).
you can either pass the data by using a lookup module that will read
the files and make th
The role is updating /etc/group and /etc/gshadow system files from various
sources, such as ldap and a central file which is now in Ansible. That's
why I created a role and put all related data into it: "defaults", "files",
"library" and "tasks" directories. Data in "defaults" is read by the
ma
Hi, it might be easier to use lookup plugins to pass the data to the
module, I really would need to know what the modules does and how it works
before I can tell you the best approach.
On Thursday, June 4, 2015, wrote:
> Hi Brian,
>
> I've written a Python module in a role using data that I'm go
Hello,
I've created a role with its main task using my Python module that should
access a yaml file located in files dir of the role:
roles
my_role
tasks
main.yml
library
my_module
files
my_file.yml
>From my_module (Python), how ca
