Change Details

As a **developer**, **I want** to test if my playbooks do what they're supposed to do, **so that** me and others can test my playbooks before they are applied to production servers Acceptance Criteria: - A `Vagrantfile` in our infrastructure repository that can spin up a VM (with the corresponding Ubuntu version) for each of your roles outlined in `servers.ini`. Each machine should have a fixed IP in a local, private network. - an alternative `servers.ini`for the Vagrant environment - A description in the README how to invoke `ansible_playbook` with the `vagrant` user and its private key (e.g. `-e ansible_ssh_private_key_file=.vagrant/machines/default/virtualbox/private_key`) Background: - [[ https://www.vagrantup.com/docs/multi-machine/ | Vagrant Multi-Machine setup ]]

As a **developer**, **I want** to test if my playbooks do what they're supposed to do, **so that** me and others can test my playbooks before they are applied to production servers Acceptance Criteria: - A `Vagrantfile` in our infrastructure repository that can spin up a VM (with the corresponding Ubuntu version) for each of your roles outlined in `servers.ini`. Each machine should have a fixed IP in a local, private network. - an alternative `servers.ini`for the Vagrant environment. Use the `vagrant` user and its private key (e.g. `ansible_ssh_private_key_file=.vagrant/machines/default/virtualbox/private_key`) - A description in the README how to invoke `ansible_playbook` in the test environment. Background: - [[ https://www.vagrantup.com/docs/multi-machine/ | Vagrant Multi-Machine setup ]]

As a **developer**, **I want** to test if my playbooks do what they're supposed to do, **so that** me and others can test my playbooks before they are applied to production servers Acceptance Criteria: - A `Vagrantfile` in our infrastructure repository that can spin up a VM (with the corresponding Ubuntu version) for each of your roles outlined in `servers.ini`. Each machine should have a fixed IP in a local, private network. - an alternative `servers.ini`for the Vagrant environment. Use the `vagrant` user and its private key (e.g. `ansible_ssh_private_key_file=.vagrant/machines/default/virtualbox/private_key`) - A description in the README how to invoke `ansible_playbook` with the `vagrant` user and its private key (e.g. `-e ansible_ssh_private_key_file=.vagrant/machines/default/virtualbox/private_key`)in the test environment. Background: - [[ https://www.vagrantup.com/docs/multi-machine/ | Vagrant Multi-Machine setup ]]