|ANSIBLE-VAULT(1)||System administration commands||ANSIBLE-VAULT(1)|
Because Ansible tasks, handlers, and other objects are data, these can also be encrypted with vault. If you'd like to not expose what variables you are using, you can keep an individual task file entirely encrypted.
- encrypt the supplied file using the provided vault secret
- re-encrypt a vaulted file with a new secret, the previous secret is
- encrypt the supplied string using the provided vault secret
- open and decrypt an existing vaulted file in an editor, that will be
encrypted again when closed
- create and open a file in an editor that will be encrypted with the
provided vault secret when closed
- decrypt the supplied file using the provided vault secret
- open, decrypt and view an existing vaulted file using a pager using the supplied vault secret
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.
~/.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.
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>