Setup Vagrant file for testing/developing INBOX stuff on google

[taoeffect]

Place testing IMAP server (the one we're migrating from) IP / password info in private/credentials.yml and retrieve them from there.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/7039781-setup-vagrant-file-for-testing-developing-inbox-stuff-on-google?utm_campaign=plugin&utm_content=tracker%2F8064840&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F8064840&utm_medium=issues&utm_source=github).

[bgw]

There's a few ways to load these kinds of credentials.

• Load the credentials in vagrant, and pass them to ansible
• In the top-level playbooks, load secrets using vars_files
• Separate the secrets needed by vagrant and by ansible, and use ansible's vault feature for secrets needed only by ansible.

[taoeffect]

I should have been clearer about what I need help with:

• Using the private/credentials.yml file in conjunction with Vagrant and Ansible to test migration from existing test IMAP server.
• Getting the machine provisioned and running the first place
• Then "re-doing" just the migration part as I make changes (without re-creating and destroying the machine)

[bgw]

• Using the private/credentials.yml file in conjunction with Vagrant and Ansible to test migration from existing test IMAP server.

Modify test.yml so it runs the mail migration steps when the necessary credentials are supplied, and skips them when they aren't.

• Getting the machine provisioned and running the first place

Depends on the exact problems you encounter in the process.

• Then "re-doing" just the migration part as I make changes (without re-creating and destroying the machine)

vagrant provision will re-run ansible without destroying and recreating the VM.