table of contents
ANSIBLE-PULL(1) | System administration commands | ANSIBLE-PULL(1) |
NAME¶
ansible-pull - pulls playbooks from a VCS repo and executes them for the local host
SYNOPSIS¶
- usage: ansible-pull [-h] [--version] [-v] [-k]
- [--private-key PRIVATE_KEY_FILE] [-u REMOTE_USER] [-c CONNECTION] [-T TIMEOUT] [--ssh-common-args SSH_COMMON_ARGS] [--sftp-extra-args SFTP_EXTRA_ARGS] [--scp-extra-args SCP_EXTRA_ARGS] [--ssh-extra-args SSH_EXTRA_ARGS] [--vault-id VAULT_IDS] [--ask-vault-password | --vault-password-file VAULT_PASSWORD_FILES] [-e EXTRA_VARS] [-t TAGS] [--skip-tags SKIP_TAGS] [-i INVENTORY] [--list-hosts] [-l SUBSET] [-M MODULE_PATH] [-K] [--purge] [-o] [-s SLEEP] [-f] [-d DEST] [-U URL] [--full] [-C CHECKOUT] [--accept-host-key] [-m MODULE_NAME] [--verify-commit] [--clean] [--track-subs] [--check] [--diff] [playbook.yml [playbook.yml ...]]
DESCRIPTION¶
Used to pull a remote copy of ansible on each managed node, each set to run via cron and update playbook source via a source repository. This inverts the default push architecture of ansible into a pull architecture, which has near-limitless scaling potential.
The setup playbook can be tuned to change the cron frequency, logging locations, and parameters to ansible-pull. This is useful both for extreme scale-out as well as periodic remediation. Usage of the 'fetch' module to retrieve logs from ansible-pull runs would be an excellent way to gather and analyze remote logs from ansible-pull.
COMMON OPTIONS¶
--accept-host-key
--ask-vault-password, --ask-vault-pass
--check
--clean
--diff
--full
--list-hosts
--private-key 'PRIVATE_KEY_FILE', --key-file 'PRIVATE_KEY_FILE'
--purge
--scp-extra-args 'SCP_EXTRA_ARGS'
--sftp-extra-args 'SFTP_EXTRA_ARGS'
--skip-tags
--ssh-common-args 'SSH_COMMON_ARGS'
--ssh-extra-args 'SSH_EXTRA_ARGS'
--track-subs
--vault-id
--vault-password-file, --vault-pass-file
--verify-commit
--version
-C 'CHECKOUT', --checkout 'CHECKOUT'
-K, --ask-become-pass
-M, --module-path
-T 'TIMEOUT', --timeout 'TIMEOUT'
-U 'URL', --url 'URL'
-c 'CONNECTION', --connection 'CONNECTION'
-d 'DEST', --directory 'DEST'
-e, --extra-vars
-f, --force
-h, --help
-i, --inventory, --inventory-file
-k, --ask-pass
-l 'SUBSET', --limit 'SUBSET'
-m 'MODULE_NAME', --module-name 'MODULE_NAME'
-o, --only-if-changed
-s 'SLEEP', --sleep 'SLEEP'
-t, --tags
-u 'REMOTE_USER', --user 'REMOTE_USER'
-v, --verbose
ENVIRONMENT¶
The following environment variables may be specified.
ANSIBLE_CONFIG -- Specify override location for the ansible config file
Many more are available for most options in ansible.cfg
For a full list check https://docs.ansible.com/. or use the ansible-config command.
FILES¶
/etc/ansible/ansible.cfg -- Config file, used if present
~/.ansible.cfg -- User config file, overrides the default config if present
./ansible.cfg -- Local config file (in current working directory) assumed to be 'project specific' and overrides the rest if present.
As mentioned above, the ANSIBLE_CONFIG environment variable will override all others.
AUTHOR¶
Ansible was originally written by Michael DeHaan.
COPYRIGHT¶
Copyright © 2018 Red Hat, Inc | Ansible. Ansible is released under the terms of the GPLv3 license.
SEE ALSO¶
ansible (1), ansible-config (1), ansible-console (1), ansible-doc (1), ansible-galaxy (1), ansible-inventory (1), ansible-playbook (1), ansible-vault (1)
Extensive documentation is available in the documentation site: <https://docs.ansible.com>. IRC and mailing list info can be found in file CONTRIBUTING.md, available in: <https://github.com/ansible/ansible>
Ansible 2.11.6 |