Re: [ansible-project] How to point `vars` to matching `vault_`?

Confirmed, works! Thank you to both! On Friday, September 23, 2016 at 10:59:51 AM UTC-5, Andrew Feller wrote: > > Within group_vars there needs to be a directory named after the group > which contains vars(.yml) and vault(.yml) > > Kai's example uses the group named webservers and works > --

Re: [ansible-project] How to point `vars` to matching `vault_`?

Hi, Kai; Thanks for your reply. I followed your instructions (which is what I had already tried) but it doesn't work for me. Here is my tree: 10:35 $ tree . ├── group_vars │ ├── standalone.yml │ ├── vault.yml And here is the command I am running: ansible-playbook -v -i

[ansible-project] How to point `vars` to matching `vault_`?

I'm using vault for the first time (previously used dotenv) and am following the instructions here . Specifically, the line: You should adjust the variables in the vars file to point to the

[ansible-project] Re: Variable definition best practice

I've never set vars inside the playbook but I've seen it done. I'm not really a fan of that structure because different applications/environments might use the same role and having the vars set within the playbooks can cause a lot of problems or unintended consequences. Without know your

[ansible-project] MODULE FAILURE - Error in unarchive module (don't unarchive if file already exists)

I'm running the following with the intention of unarchiving a zip if the target file doesn't exist while not running it if it does exist: - name: Install Consul > > unarchive: creates=no > > copy=no > > src=/tmp/{{ consul_ubuntu_pkg }} > >