use `localhost` instead of the host name, unless you defined 'localhost' in
your inventory it should avoid remote connections and use in the 'local'
connection plugin.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
Thanks for the tip about delegation, donno how I have not used it yet. Do
you have to change security settings when you do though? I am getting an
SSH unreachable error on just that one delegate task (not the rest of them).
On Monday, August 22, 2016 at 11:45:58 AM UTC-4, Josh Smift wrote:
>
>
SO> Thanks for the tip about delegation, donno how I have not used it yet.
SO> Do you have to change security settings when you do though? I am
SO> getting an SSH unreachable error on just that one delegate task (not
SO> the rest of them).
I think your Ansible control host would need to be able
you can do in 1 task:
- template:
delegate_to: "{{item}}"
with_items:
- "{{inventory_hostname}}" # or ansible_host, depends on your inventory
- central-host
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Project"
SO> Anybody know of a way to deploy a template to multiple servers, but
SO> have each configuration simultaneously centralized on another server?
How about delegate_to?
- hosts: myservers
tasks:
- name: put foo on myservers
template:
src: foo.txt.j2
Anybody know of a way to deploy a template to multiple servers, but have
each configuration simultaneously centralized on another server? I do not
want the servers speaking with each other, so synchronize would not really
be an option. I would also prefer not to use fetch, as having the
