I was kind of expecting something like that... It's a pity, but thanks a
lot for clarifying this!
El mar, 24 may 2022 a la(s) 10:58, Brian Coca (bc...@redhat.com) escribió:
> no such facility exists, each task runs in a fork so even if you
> change the environment successfully with a action plugi
no such facility exists, each task runs in a fork so even if you
change the environment successfully with a action plugin, it would not
persist for the next task.
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To u
Thanks for your answer Brian! So you say there's no way? It doesn't have
to be inline in the task itself. If there's some task that can modify the
controller environment beforehand that's good enough...
El jueves, 19 de mayo de 2022 a la(s) 10:33:57 UTC-3, Brian Coca escribió:
> The 'environme
The 'environment' keyword ONLY applies to the modules, all other
lookups share the controller environment and cannot be modified
inline.
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group
Hi community! I have a simple, newbie question related to setting the
environment for plugins. This playbook illustrates my problem:
---
- name: env behaviour
hosts: localhost
gather_facts: no
environment:
MY_VAR: foo
tasks:
- name: shell w/environment
shell: echo $MY_VAR
