e2e: Terraform updates to support framework deploys #6948
Conversation
|
|
||
| output "provisioning" { | ||
| description = "output to a file to be use w/ E2E framework -provision.terraform" | ||
| value = jsonencode( |
There was a problem hiding this comment.
wow this is p cool - didn't realise tf had list templating like this
There was a problem hiding this comment.
I'm sure the Terraform team would be terrified if they saw this. 😀
tgross
force-pushed
the
e2e_provisioning_terraform_scripts
branch
3 times, most recently
from
18f029e to
be92c27
Compare
|
I've found a couple of cleanup items to wrap up here for Windows. |
The e2e framework instantiates clients for Nomad/Consul but the provisioning of the actual Nomad cluster is left to Terraform. The Terraform provisioning process uses `remote-exec` to deploy specific versions of Nomad so that we don't have to bake an AMI every time we want to test a new version. But Terraform treats the resulting instances as immutable, so we can't use the same tooling to update the version of Nomad in-place. This is a prerequisite for upgrade testing. This changeset: * provides Terraform output that written to JSON used by the framework to configure provisioning via `terraform output provisioning`. * provides Terraform output that can be used by test operators to configure their shell via `$(terraform output environment)` * drops `remote-exec` provisioning steps from Terraform * makes changes to the deployment scripts to ensure they can be run multiple times w/ different versions against the same host.
tgross
force-pushed
the
e2e_provisioning_terraform_scripts
branch
from
be92c27 to
06b31c5
Compare
|
I've rebased this and the target branch off master and did a full end-to-end test (including Windows) with #6949. Once tests pass I'll merge this and then open a PR with the combined branch vs master. |
|
I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions. |
The e2e framework instantiates clients for Nomad/Consul but the provisioning of the actual Nomad cluster is left to Terraform. The Terraform provisioning process uses
remote-execto deploy specific versions of Nomad so that we don't have to bake an AMI every time we want to test a new version. But Terraform treats the resulting instances as immutable, so we can't use the same tooling to update the version of Nomad in-place. This is a prerequisite for upgrade testing.This changeset:
terraform output provisioning(consumed by e2e: deploy Nomad from testing framework #6949)$(terraform output environment)remote-execprovisioning steps from Terraform