Vagrant test env

[apentori]

Add usage of vagrant to deploy a local test environment

[jakubgs]

I don't know if I like this. I'd rather not clutter up the template with extra stuff like that.

One one hand I do agree that it's good to have a way to test things locally. But on another hand
this repo should be slim, and have only things essentialy for a fleet setup. I'd rather keep the Makefile as small as possible. This setup is useful, but it is optional.

Some other issues include:

• You can't create something like ansible/inventory/test since many repos already have that.
• Same goes for ansible/group_vars/test.yml, it's a file that can easily already be in fleet repos.

If I was doing something like this I'd write a script of some sort to put in infra-utils that would call Vagrant and Ansible for you. For example:

• You don't need a group_vars file because that could be passed to Ansible via -e flag.
• You don't need a inventory file because that could be passed to Ansible via -i flag.
• All you need is a Vagrantfile, and that could be created by the script.
• The only thing we could add to the template is Vagrantfile and .vagrant to .gitignore.

What I'd envision is if you're in any repo, and you want to test playbook abc, instead of doing:

ansible-playbook ansible/abc.yml

You could do:

~/work/infra-utils/ansible/vm-playbook.py ansible/abc.yml

Which would:

1. Create a Vagrantfile if not present
2. Start a virtual machine if not already running.
3. Run Ansible in that VM using flags like -e, -i, --user, and soon.

• It could also parse the playbook file to apply to the host the correct groups

What do you think?