luxolus
/
open-nomad
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity
open-nomad/e2e/terraform/terraform.tfvars

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

13 lines
496 B
Plaintext
Raw Normal View History

e2e: swap bionic image for jammy (#15220)
2022-11-16 16:37:18 +00:00
region = "us-east-1"
instance_type = "t3a.medium"
server_count = "3"
client_count_ubuntu_jammy_amd64 = "4"
client_count_windows_2016_amd64 = "1"
volumes = true
e2e: make dev cluster the default Terraform vars file (#9202) Most of the time that a human is running the TF provisioning, they want the "dev cluster" which is going to deploy an OSS sha, with fewer targets and configuration alternatives. But the default `terraform.tfvars` is the nightly E2E run. Because the nightly run is automated, there's no reason we can't have it pick a non-default `terraform.full.tfvars` file and have the default be the dev cluster.
2020-10-28 14:01:42 +00:00
E2E with HCP Consul/Vault (#12267) Use HCP Consul and HCP Vault for the Consul and Vault clusters used in E2E testing. This has the following benefits: * Without the need to support mTLS bootstrapping for Consul and Vault, we can simplify the mTLS configuration by leaning on Terraform instead of janky bash shell scripting. * Vault bootstrapping is no longer required, so we can eliminate even more janky shell scripting * Our E2E exercises HCP, which is important to us as an organization * With the reduction in configurability, we can simplify the Terraform configuration and drop the complicated `provision.sh`/`provision.ps1` scripts we were using previously. We can template Nomad configuration files and upload them with the `file` provisioner. * Packer builds for Linux and Windows become much simpler. tl;dr way less janky shell scripting!
2022-03-18 13:27:28 +00:00
nomad_local_binary = "../../pkg/linux_amd64/nomad"
nomad_local_binary_client_windows_2016_amd64 = ["../../pkg/windows_amd64/nomad.exe"]
e2e: set default version for dev cluster (#9208)
2020-10-28 20:50:20 +00:00
E2E with HCP Consul/Vault (#12267) Use HCP Consul and HCP Vault for the Consul and Vault clusters used in E2E testing. This has the following benefits: * Without the need to support mTLS bootstrapping for Consul and Vault, we can simplify the mTLS configuration by leaning on Terraform instead of janky bash shell scripting. * Vault bootstrapping is no longer required, so we can eliminate even more janky shell scripting * Our E2E exercises HCP, which is important to us as an organization * With the reduction in configurability, we can simplify the Terraform configuration and drop the complicated `provision.sh`/`provision.ps1` scripts we were using previously. We can template Nomad configuration files and upload them with the `file` provisioner. * Packer builds for Linux and Windows become much simpler. tl;dr way less janky shell scripting!
2022-03-18 13:27:28 +00:00
# For testing enterprise, set via --var:
# nomad_license = <content of Nomad license>