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

33 lines
740 B
Makefile
Raw Normal View History

e2e: testing reliability (#7701) * pin CSI plugin versions * ensure failing CSI tests clean up * allow NOMAD_SHA env var to override makefile
2020-04-13 14:25:24 +00:00
NOMAD_SHA ?= $(shell git rev-parse HEAD)
e2e: add helper to Makefile for local file deployments (#7822)
2020-04-28 20:15:58 +00:00
PKG_PATH = $(shell pwd)/../../pkg/linux_amd64/nomad
e2e: add a convenient creation script Add a convenience Makefile for creating e2e environment for manual debugging.
2020-04-09 14:54:30 +00:00
dev-cluster:
e2e: provision cluster entirely through Terraform (#8748) Have Terraform run the target-specific `provision.sh`/`provision.ps1` script rather than the test runner code which needs to be customized for each distro. Use Terraform's detection of variable value changes so that we can re-run the provisioning without having to re-install Nomad on those specific hosts that need it changed. Allow the configuration "profile" (well-known directory) to be set by a Terraform variable. The default configurations are installed during Packer build time, and symlinked into the live configuration directory by the provision script. Detect changes in the file contents so that we only upload custom configuration files that have changed between Terraform runs
2020-09-18 15:27:24 +00:00
terraform apply -auto-approve \
e2e: set default version for dev cluster (#9208)
2020-10-28 20:50:20 +00:00
-var="nomad_sha=$(NOMAD_SHA)" \
-var="nomad_version="
e2e: provision cluster entirely through Terraform (#8748) Have Terraform run the target-specific `provision.sh`/`provision.ps1` script rather than the test runner code which needs to be customized for each distro. Use Terraform's detection of variable value changes so that we can re-run the provisioning without having to re-install Nomad on those specific hosts that need it changed. Allow the configuration "profile" (well-known directory) to be set by a Terraform variable. The default configurations are installed during Packer build time, and symlinked into the live configuration directory by the provision script. Detect changes in the file contents so that we only upload custom configuration files that have changed between Terraform runs
2020-09-18 15:27:24 +00:00
terraform output environment
e2e: add a convenient creation script Add a convenience Makefile for creating e2e environment for manual debugging.
2020-04-09 14:54:30 +00:00
e2e: add helper to Makefile for local file deployments (#7822)
2020-04-28 20:15:58 +00:00
dev-cluster-from-local:
e2e: provision cluster entirely through Terraform (#8748) Have Terraform run the target-specific `provision.sh`/`provision.ps1` script rather than the test runner code which needs to be customized for each distro. Use Terraform's detection of variable value changes so that we can re-run the provisioning without having to re-install Nomad on those specific hosts that need it changed. Allow the configuration "profile" (well-known directory) to be set by a Terraform variable. The default configurations are installed during Packer build time, and symlinked into the live configuration directory by the provision script. Detect changes in the file contents so that we only upload custom configuration files that have changed between Terraform runs
2020-09-18 15:27:24 +00:00
terraform apply -auto-approve \
e2e: set default version for dev cluster (#9208)
2020-10-28 20:50:20 +00:00
-var="nomad_local_binary=$(PKG_PATH)" \
-var="nomad_version="
e2e: provision cluster entirely through Terraform (#8748) Have Terraform run the target-specific `provision.sh`/`provision.ps1` script rather than the test runner code which needs to be customized for each distro. Use Terraform's detection of variable value changes so that we can re-run the provisioning without having to re-install Nomad on those specific hosts that need it changed. Allow the configuration "profile" (well-known directory) to be set by a Terraform variable. The default configurations are installed during Packer build time, and symlinked into the live configuration directory by the provision script. Detect changes in the file contents so that we only upload custom configuration files that have changed between Terraform runs
2020-09-18 15:27:24 +00:00
terraform output environment
e2e: add helper to Makefile for local file deployments (#7822)
2020-04-28 20:15:58 +00:00
e2e: add a convenient creation script Add a convenience Makefile for creating e2e environment for manual debugging.
2020-04-09 14:54:30 +00:00
clean:
terraform destroy -auto-approve
e2e: provision cluster entirely through Terraform (#8748) Have Terraform run the target-specific `provision.sh`/`provision.ps1` script rather than the test runner code which needs to be customized for each distro. Use Terraform's detection of variable value changes so that we can re-run the provisioning without having to re-install Nomad on those specific hosts that need it changed. Allow the configuration "profile" (well-known directory) to be set by a Terraform variable. The default configurations are installed during Packer build time, and symlinked into the live configuration directory by the provision script. Detect changes in the file contents so that we only upload custom configuration files that have changed between Terraform runs
2020-09-18 15:27:24 +00:00
full-cluster:
terraform apply -auto-approve \
-var="nomad_sha=$(NOMAD_SHA)" \
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
-var-file=terraform.full.tfvars
e2e: provision cluster entirely through Terraform (#8748) Have Terraform run the target-specific `provision.sh`/`provision.ps1` script rather than the test runner code which needs to be customized for each distro. Use Terraform's detection of variable value changes so that we can re-run the provisioning without having to re-install Nomad on those specific hosts that need it changed. Allow the configuration "profile" (well-known directory) to be set by a Terraform variable. The default configurations are installed during Packer build time, and symlinked into the live configuration directory by the provision script. Detect changes in the file contents so that we only upload custom configuration files that have changed between Terraform runs
2020-09-18 15:27:24 +00:00
plan-dev-cluster:
terraform plan \
e2e: set default version for dev cluster (#9208)
2020-10-28 20:50:20 +00:00
-var="nomad_sha=$(NOMAD_SHA)" \
-var="nomad_version="
e2e: provision cluster entirely through Terraform (#8748) Have Terraform run the target-specific `provision.sh`/`provision.ps1` script rather than the test runner code which needs to be customized for each distro. Use Terraform's detection of variable value changes so that we can re-run the provisioning without having to re-install Nomad on those specific hosts that need it changed. Allow the configuration "profile" (well-known directory) to be set by a Terraform variable. The default configurations are installed during Packer build time, and symlinked into the live configuration directory by the provision script. Detect changes in the file contents so that we only upload custom configuration files that have changed between Terraform runs
2020-09-18 15:27:24 +00:00
plan-full-cluster:
terraform plan \
-var="nomad_sha=$(NOMAD_SHA)" \
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
-var-file=terraform.full.tfvars