History

Preetha Appan 419a2682b0 update to Consul 1.4.0 for e2e tests		2019-01-24 09:52:15 -06:00
..
configs	Terraform configs for e2e tests	2018-12-17 11:40:09 -06:00
shared	update to Consul 1.4.0 for e2e tests	2019-01-24 09:52:15 -06:00
compute.tf	Terraform configs for e2e tests	2018-12-17 11:40:09 -06:00
iam.tf	Terraform configs for e2e tests	2018-12-17 11:40:09 -06:00
main.tf	e2e: Output setup instructions after terraform	2019-01-04 16:55:14 +01:00
network.tf	Terraform configs for e2e tests	2018-12-17 11:40:09 -06:00
packer.json	Terraform configs for e2e tests	2018-12-17 11:40:09 -06:00
README.md	Update README.md	2019-01-03 15:31:19 -06:00
terraform.tfvars	suggestions from code review	2018-12-17 15:06:22 -06:00
user-data-client.sh	Terraform configs for e2e tests	2018-12-17 11:40:09 -06:00
user-data-server.sh	Terraform configs for e2e tests	2018-12-17 11:40:09 -06:00

README.md

Terraform provisioner for end to end tests

This folder contains terraform resources for provisioning a nomad cluster on AWS for end to end tests. It uses a Nomad binary identified by its commit SHA that's stored in a shared s3 bucket that Nomad team developers can access. The commit SHA can be from any branch that's pushed to remote.

Use envchain to store your AWS credentials.

$ cd e2e/terraform/
$ envchain nomadaws TF_VAR_nomad_sha=<nomad_sha> terraform apply

After this step, you should have a nomad client address to point the end to end tests in the e2e folder to.

Teardown

The terraform state file stores all the info, so the nomad_sha doesn't need to be valid during teardown.

$ cd e2e/terraform/
$ envchain nomadaws TF_VAR_nomad_sha=yyyzzz terraform destroy