title: Ansible breadcrumbs:
--ask-pass
--ask-become-pass
--username=<username>
--private-key=<key>
(use /dev/null
to explicitly avoid SSH keys)ansible {all|<target>} -i <inventory> [-m <module>] [-a <module-arg>]
all -i <host>,
(with the comma).all -i localhost, --connection=local
.... -m ping
... -a <cmd>
... -a 'bash -c "nvidia-smi > /dev/null"'
ansible <...> -m setup -a 'filter=ansible_os_*'
(example fact filter)ansible-playbook <playbook>
ansible-playbook -i <hosts> <playbook>
ansible-playbook -l <group|host> <playbook>
ansible-playbook -t <tag> <playbook>
!vault ...
output directly into the configs to use the encrypted value in.~/.ansible_vault/<name>
(with appropriate parent dir perms). A generated [a-zA-Z0-9]{32}
string is more than strong enough.ansible-vault encrypt_string --vault-password-file=~/.ansible_vault/stuff
ansible-playbook --vault-password-file=<file> <...>
no_log
in tasks handling secrets.Config locations:
/etc/ansible/ansible.cfg
~/.ansible.cfg
ansible.cfg
Example config:
[defaults]
host_key_checking = false
#interpreter_python = auto
interpreter_python = /usr/bin/python3
#inventory = hosts.ini
#roles_path = ansible-roles:~/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles
#jinja2: trim_blocks:False
to avoid that. This will also make the output a little uglier with empty lines in place of unsatisfied conditionals and stuff though.Probably caused by a password-protected SSH key. Add --private-key=<keyfile>
to specify which SSH key to use or --private-key=/dev/null
to avoid using any SSH key.
{% include footer.md %}