open-nomad/e2e/consul
Tim Gross 9f05d62338
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 09:27:28 -04:00
..
input e2e: consul namespace tests from nomad ent 2021-04-19 15:35:31 -06:00
check_restart.go e2e: account for new job stop CLI exit behaviour. 2022-02-01 14:16:37 +01:00
consul.go E2E with HCP Consul/Vault (#12267) 2022-03-18 09:27:28 -04:00
namespaces.go E2E with HCP Consul/Vault (#12267) 2022-03-18 09:27:28 -04:00
namespaces_oss.go E2E with HCP Consul/Vault (#12267) 2022-03-18 09:27:28 -04:00
on_update.go e2e: remove duplicate import statements. 2021-06-11 09:37:23 +02:00
script_checks.go e2e: add tests for consul namespaces from nomad oss 2021-04-16 15:32:37 -06:00