On 19.07.2019 14:46, DT wrote:
Hi, Phil. Thanks for the response. I guess I am familiar with how
Ansible
works at the level you describe. What I'm looking for is to understand
what
is going on a bit deeper under the covers. We have all of these plugins
that seemingly execute at random times during the playbook run (Action,
Cliconf, Terminal, etc.) and I just want to know the order that they
execute and then how the output from one can be potentially used as the
input for another. Typically you would need to import the classes and
functions from one .py into another in order to make use of them, but
that
doesn't seem to be happening in the plugins. Are the outputs of the
plugins
stored in a global memory space for all other plugins to make use of
during
the playbook execution? Note that I'm referring to the plugins, not the
modules - so the stuff that sets up the environment for the modules to
actually run successfully.
I may just be asking a stupid question and it's ok for you all to tell
me
as much :-)
For the end user it doesn't matter what is executed in what order as
long as it works.
And for running Ansible from other than the bundled executables you
should use Ansible runner
https://github.com/ansible/ansible-runner
--
Kai Stian Olstad
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/63320fcc727030ec549bca6b9873838c%40olstad.com.
