Gotcha, thanks!
On Mon, May 4, 2015 at 10:37 AM, Brian Coca wrote:
> It is not the solution, but it is a workaround available now.
>
> On my list i have being able to 'delegate' facts so we can do something like:
>
> setup: set_for={{item}}
> delegate_to: "{{item}}'
> with_items: "{{groups['dbser
It is not the solution, but it is a workaround available now.
On my list i have being able to 'delegate' facts so we can do something like:
setup: set_for={{item}}
delegate_to: "{{item}}'
with_items: "{{groups['dbservers']}}
but my list is long and this is not a simple task.
--
Brian Coca
--
I have to say, that it kind of bothers me that fact "caching" is the
solution to whether or not it works. Caching is normally about
speeding things up or making them more scalable. Not about having it
actually be correct. In this instance, wouldn't relying on fact
caching break every time the cache
Another way around this is using persistent fact caching.
--
Brian Coca
--
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...@googlegr
CF> Is there a way to force ansible to gather facts on all hosts, even if
CF> you limit the playbook to one specific host?
If you don't have to use --limit per se to do it, you can get much the
same effect with something like this:
- hosts: all
gather_facts: true
- hosts: "{{ targets }
Hi all,
I'm sitting in front of a fairly complex ansible project that we're using
to set up our local development environments (multiple VMs) and there's one
role that uses the facts gathere by ansible to set up the etc/hosts file on
every VM. Unfortunately, when you want to run the playbook
