Hi, just stumpled upon the same problem. Using the cli --vault-id is not really practicable in our case. No one wants to write this long string. Vault-id seems like a nice thing.. but not really thought through. Or am I missing something?
Yours Am Mittwoch, 31. Januar 2018 12:27:05 UTC+1 schrieb [email protected]: > > Hi, > We're using vault files encrypted with multiple vault-id in our projects. > Everything works fine when we do something like: > ansible vault --vault-id generic@~/.ansible/generic-password --vault-id > prod@~/.ansible/prod-password ... > > But it's not convenient way to pass password files for each vault id as > cli arguments. > Previously, before vault-id, we used single password for everything and we > just added "vault_password_file=~/.ansible/password" into ansible.cfg. > Is there any way to add multiple password file in ansible.cfg for each > vault id? > The most straight way as for me, is to add something like this > [defaults] > vault_password_file=generic@~/.ansible/generic-password > vault_password_file=prod@~/.ansible/prod-password > > And of course it doesn't work. > But how can I do it right? > > Thanks. > -- 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/af9b097e-912a-47c9-aad9-507b9f0d1648%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
