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

Docs: Fix statements about the ansible.cfg lookup 

Related to GH-7195

[ci skip]
This commit is contained in:
Gilles Cornu 2016-04-24 16:59:19 +02:00
parent cf908d35e0
commit cdafc63a61
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
website/source/docs/provisioning/ansible_intro.html.md
View File

@ -248,10 +248,11 @@ Certain settings in Ansible are (only) adjustable via a [configuration file](htt
When shipping an Ansible configuration file it is good to know that: When shipping an Ansible configuration file it is good to know that:
- it is possible to reference an Ansible configuration file via `ANSIBLE_CONFIG` environment variable, if you want to be flexible about the location of this file. - it is possible to reference an Ansible configuration file via `ANSIBLE_CONFIG` environment variable, if you want to be flexible about the location of this file.
- `ansible-playbook` **never** looks for `ansible.cfg` in the directory that contains the main playbook file. - as of Ansible 1.5, the lookup order is the following:
- As of Ansible 1.5, the lookup order is the following:
- `ANSIBLE_CONFIG` an environment variable - `ANSIBLE_CONFIG` an environment variable
- `ansible.cfg` in the runtime current directory - `ansible.cfg` in the runtime working directory
- `.ansible.cfg` in the user home directory - `.ansible.cfg` in the user home directory
- `/etc/ansible/ansible.cfg` - `/etc/ansible/ansible.cfg`
- `ansible-playbook` doesn't look for a configuration file relative to the playbook file location (e.g. in the same directory)