Keeping your inventory in different directories solves this for you.
-i inventory/production/inventory.ini, group_vars, host_vars
-i inventory/stage/inventory.ini, group_vars, host_vars
Basically it would only see the group_vars, host_vars in that particular
directory.
Host_vars could even be sh
Do you use the same inventory for all of your playbooks? I'm not
familiar with the change that made this pattern not work, but does it
only pull in group_vars for groups in your inventory? If you used
separate inventories for each environment would this problem go away?
On Wed, Nov 5, 2014 at 12:3
>
> Is this being done because some team members might leave the team later
> and no longer need access to something?
We have 3 vaults -- one each for dev, staging, and production. They
contain all the same variables, just with different values. We gave them
all different passwords so that
It's going to be the case because we don't know if a template will
reference a variable later.
On Tue, Nov 4, 2014 at 7:09 AM, Barry Morrison wrote:
> This has been a paint point for our team as well, asking for a vault
> password when the playbook has nothing to do with vaulted items. Wish t
This has been a paint point for our team as well, asking for a vault
password when the playbook has nothing to do with vaulted items. Wish this
weren't the case.
On Thursday, October 30, 2014 3:01:01 PM UTC-7, Colin Nichols wrote:
>
> Hi all,
>
> I've been using ansible 1.6.x and I love it -- s
