open-nomad/e2e/framework/provisioning
Tim Gross b23150057a
E2E: move Nomad installation to script on remote hosts (#8706)
This changeset moves the installation of Nomad binaries out of the
provisioning framework and into scripts that are installed on the remote host
during AMI builds.

This provides a few advantages:

* The provisioning framework can be reduced in scope (with the goal of moving
  most of it into the Terraform stack entirely).
* The scripts can be arbitrarily complex if we don't have to stuff them into
  ssh commands, so it's easier to make them idempotent. In this changeset, the
  scripts check the version of the existing binary and don't re-download when
  using the `--nomad_sha` or `--nomad_version` flags.
* The scripts can be OS/distro specific, which helps in building new test
  targets.
2020-08-20 16:10:00 -04:00
..
config_terraform.go e2e: update framework to allow deploying Nomad (#6969) 2020-01-22 08:48:52 -05:00
config_vagrant.go e2e: update framework to allow deploying Nomad (#6969) 2020-01-22 08:48:52 -05:00
default.go e2e: update framework to allow deploying Nomad (#6969) 2020-01-22 08:48:52 -05:00
deploy.go E2E: move Nomad installation to script on remote hosts (#8706) 2020-08-20 16:10:00 -04:00
example.json e2e: update framework to allow deploying Nomad (#6969) 2020-01-22 08:48:52 -05:00
linux_runner.go e2e: rename linux runner to avoid implicit build tag (#7070) 2020-02-04 10:55:38 -05:00
preprovision.go e2e: update framework to allow deploying Nomad (#6969) 2020-01-22 08:48:52 -05:00
provisioning.go e2e: update framework to allow deploying Nomad (#6969) 2020-01-22 08:48:52 -05:00
ssh_runner.go e2e: rename linux runner to avoid implicit build tag (#7070) 2020-02-04 10:55:38 -05:00
targets.go e2e: update framework to allow deploying Nomad (#6969) 2020-01-22 08:48:52 -05:00