On 21 May 2014 16:53, Hagai Kariti <[email protected]> wrote: > It's really the same idea as group_vars. For each group a host is a member > of, two files are included: > - The file under group_vars/, as usual > - The vaulted file under the vaulted group_vars dir > > This allows you to separate the sensitive and normal parts of your > group_vars, so that you won't lose version control on the normal parts. >
OK, actually, you already can do something similar, what I do: for each group X I have a directory group_vars/X/ every file in that dir will be loaded for group X then you van have a group_vars/X/secret.yml e.g. which is vaulted. Would that work for you? -- 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/CAEhzMJAO%3DWwrx%3D4Rf79SwrzLffci7sO%2B3OvPkc63ckWQs%2Bhdig%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
