This simplifies the stand-up of a sandbox:

Only 2 main Vagrant calls are now needed (`vagrant up` and `vagrant up machine1`).
This PR only updates the Vagrant Virtualbox setup. The Vagrant Libvirt and Terraform
still need to be updated.

This uses docker-compose as the entry point for standing up the stack and makes the stand-up
of the sandbox more portal. Vagrant and Terraform are only responsible for standing up infrastructure
and then running docker-compose, not for running any glue scripts.

The docker-compose calls out to single-shot services to do all the glue required to get the fully
functional Tinkerbell stack up and running. All the single-shot services are idempotent.
This increases portability and the development iteration loop. This also simplifies the required
steps needed to get a fully functioning sandbox up and running.

This is intended to help people looking to get started by getting them to a provisioned
machine quicker and more easily.

Signed-off-by: Jacob Weinstock <jakobweinstock@gmail.com>

releases/script/release-binaries.sh

@@ -0,0 +1,29 @@
+#!/usr/bin/env bash
+# shellcheck disable=SC1091,SC2086
+
+source ./current_versions.sh
+
+go run cmd/getbinariesfromquay/main.go \
+	-binary-to-copy /usr/bin/hegel \
+	-image docker://${TINKERBELL_TINK_HEGEL_IMAGE} \
+	-program hegel
+
+go run cmd/getbinariesfromquay/main.go \
+	-binary-to-copy /usr/bin/boots \
+	-image docker://${TINKERBELL_TINK_BOOTS_IMAGE} \
+	-program boots
+
+go run cmd/getbinariesfromquay/main.go \
+	-binary-to-copy /usr/bin/tink-worker \
+	-image docker://${TINKERBELL_TINK_WORKER_IMAGE} \
+	-program tink-worker
+
+go run cmd/getbinariesfromquay/main.go \
+	-binary-to-copy /usr/bin/tink-server \
+	-image docker://${TINKERBELL_TINK_SERVER_IMAGE} \
+	-program tink-server
+
+go run cmd/getbinariesfromquay/main.go \
+	-binary-to-copy /usr/bin/tink \
+	-image docker://${TINKERBELL_TINK_CLI_IMAGE} \
+	-program tink