3 ms·
That's not an inherent bottleneck in Ansible. https://docs.ansible.com/ansible/latest/cli/ansible-pull.html https://docs.ansible.com/ansible/latest/cli/ansible-
by zeckalpha 7y ago
That's not an inherent bottleneck in Ansible. https://docs.ansible.com/ansible/latest/cli/ansible-pull.html https://docs.ansible.com/ansible/latest/cli/ansible-pull.htm...
There are other benefits of using this automation, namely that it removes manual application of changes.
- perlgeek 7y agoThe problem with ansible-pull is that you can no longer use it coordinate changes across machines, which is very useful for deployments for example.
- zeckalpha 7y agoWhat's preventing that?
- dmw_ng 7y agoI mean sure, just copying Ansible to the target machine and running it locally 'fixes' things, but at what point should it still be considered Ansible? You lose so much with -local, at least: - centralized vault, target nodes need access to secrets - "serial:" no longer available, you can't do rolling upgrades any more - "hostvars" no longer available, you can't query facts from other machines - no centralized trigger mechanism, status or failure reporting etc. Put another way, you could claim ansible-local fixes things for the same reason you could claim bash is network-aware agentless automation because you can copy shell scripts between machines
- aeontech 7y agoTime to add “skilled in network-aware agentless automation” to my resume!