In this thread though Dehaan said this should work-> > I just tried this on 1.9.1 I have /group_vars/staging/staging.yml and > /group_vars/staging/secrets.yml and it seems to me that it is not merging > the files properly. >
But others said this was a problem. I just don't think this is documented well. If its not supposed to work I guess it shouldn't work :( On Sunday, September 11, 2016 at 2:11:46 PM UTC-4, Dick Davies wrote: > > Are you sure that's the way things are supposed to work? > > I'd have expected individual hosts to be under host_vars/leaf01 , not > nested under a group (remember, a host can be in multiple groups). > > so your layout would be more: > > . > ├── group_vars > │ ├── all > │ └── leaf > ├── host_vars > │ ├── leaf01 > │ └── leaf02 > └── hosts > > > On 10 September 2016 at 19:02, 'Sean Cavanaugh' via Ansible Project > <[email protected] <javascript:>> wrote: > > I am curious if there was follow-up to this. I am seeing something > similar > > for a customer I am working on. > > > > If I put all my variables under group_vars/all (where all is a flat file > in > > yml syntax) it works fine. > > If I move one device out of group_vars/all to group_vars/leaf/leaf01 all > > devices work great. (where leaf corresponds to a group within my > Ansible > > hosts file). > > As soon as I do group_vars/leaf/leaf01 and leaf02 it can't find leaf01 > > anymore. leaf02 will work but not leaf01. (where leaf01 and leaf02 are > > hosts in my ansible hosts file both in the group leaf) > > > > Do they have to end with .yml? Is this not how group_vars works? Just > > trying to make folders to break up variables for simplification. > > (I am running on Ansible 2.1.1) > > > > On Saturday, August 8, 2015 at 4:59:32 PM UTC-4, Serge van Ginderachter > > wrote: > >> > >> > >> On 7 August 2015 at 20:17, <[email protected]> wrote: > >>> > >>> I just tried this on 1.9.1 I have /group_vars/staging/staging.yml and > >>> /group_vars/staging/secrets.yml and it seems to me that it is not > merging > >>> the files properly. > >>> > >>> I have an api variable in the staging file which doesnt exist in the > >>> secrets file. When I run the playbook it complains that the api > variable > >>> doesnt exist. If I either remove the secrets file or add the api > variable to > >>> the secrets file then it works. > >> > >> > >> > >> If that would be true it would be a bug, and you would need to present > us > >> a minimal example on how to reproduce it. > >> > >> That being said, I use this feature everywhere around and i know i > works. > >> It might be some corner case of course, which would only become clear > when > >> being able to reproduce it. > >> > >> Can you make a minimal example that reproduces this, and show us the > >> needed files? > >> > >> Thanks, > >> > >> > >> Serge > > > > -- > > You received this message because you are subscribed to the Google > Groups > > "Ansible Project" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to [email protected] <javascript:>. > > To post to this group, send email to [email protected] > <javascript:>. > > To view this discussion on the web visit > > > https://groups.google.com/d/msgid/ansible-project/95184094-6d7f-41f7-94aa-8d16521025d8%40googlegroups.com. > > > > > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/66b7416b-d18c-4569-ad42-76b72149f8a1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
