OK, I see that this behavior change is being shown as a bug fix in 2.1.2:
* Fixed a bug where a group_vars or host_vars directory in the current
> working directory would be used (and would take precedence) over those in
> the inventory and/or playbook directory.
It would be nice if the group_
Is it possible that previously Ansible looked for group_vars in the current
directory (i.e. a sub-directory of the current one)?
Because of multiple inventory files, I put inventory files in a
sub-directory; in this structure:
project/
├── group_vars/
│ └── all.yml
├── playbooks/
│
Ansible has no concept of 'project', group/host_vars MUST be adjacent to
either inventory or the play and should be picked up automatically if they
match an group or host from inventory.
The vars_files will look for relative paths in a 'vars/' directory adjacent
to play or relative to the play, va
I ran into this issue as well. I decided to write an action plugin called
include_vars_dir. This will sort the files in alphabetical order and
include them. This also works in a role as well. I am in the process of
writing a test suite, before making the PR. If you are interested in
checking th
I just posted about this too, it looks like a bug to me.
- David
On Thursday, August 18, 2016 at 7:41:27 PM UTC+3, Vincent Jørgensen wrote:
>
> Hi all, I have an ansible project with a groups_vars directory, with a
> subdirectory called all beneath it, like so:
> /project/group_vars/all/ami.yml
