haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Ansible Docs: Tip to ship a local `ansible.cfg` 

Hint motivated by misleading situations reported in #2302.
This commit is contained in:
Gilles Cornu 2014-02-25 06:57:10 +01:00
parent f83f863d4d
commit 84eb0d972c
1 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
website/docs/source/v2/provisioning/ansible.html.md
View File

@ -217,4 +217,12 @@ Vagrant is designed to provision [multi-machine environments](/v2/multi-machine)
ansible.limit = 'all'
end
end
```
```
### Provide a local `ansible.cfg` file
Certain settings in Ansible are (only) adjustable via a [configuration file](http://docs.ansible.com/intro_configuration.html), and you might want to ship such a file in your Vagrant project.
As `ansible-playbook` command looks for local [`ansible.cfg`] configuration file in its *current directory* (but not in the directory that contains the main playbook), you have to store this file adjacent to your Vagrantfile.
Note that it is also possible to reference an Ansible configuration file via `ANSIBLE_CONFIG` environment variable, if you want to be flexible about the location of this file.