3 ms·
And its companion, ansible-pull which can periodically run to sync changes _onto_ a machine which doesn't otherwise allow inbound connections: https://docs.ansi
by mdaniel 6y ago
And its companion, ansible-pull which can periodically run to sync changes _onto_ a machine which doesn't otherwise allow inbound connections: https://docs.ansible.com/ansible/2.10/user_guide/playbooks_intro.html#ansible-pull https://docs.ansible.com/ansible/2.10/user_guide/playbooks_i...
In your scenario, once those changes are captured, they can be written into `/etc/ansible/facts.d` and they'll show up in future playbook runs: https://docs.ansible.com/ansible/2.10/user_guide/playbooks_vars_facts.html#facts-d-or-local-facts https://docs.ansible.com/ansible/2.10/user_guide/playbooks_v...
- dreamcompiler 6y agoAt the moment I'm using git hooks on bare repos on a deployment machine to automatically build detached work trees whenever someone pushes the deployment branch. This works well because no secret keys need exist on the deployment machine. Even if encrypted, I don't want secret keys sitting on a deployment machine. Does ansible pull require a secret ssh key on the pulling machine? Seems like it would but I don't remember.
- mdaniel 6y agoIt would only require credentials if you need them to fetch from a private git repo (or other protected playbook source); otherwise it (traditionally) uses the "local" connection, meaning it will launch python subprocesses rather than trying to ssh into localhost