Without this docker-compose complains about depends_on config settings:

> ERROR: The Compose file './docker-compose.yml' is invalid because:
> services.tink-server.depends_on.generate-tls-certs.condition contains "service_completed_successfully", which is an invalid type, it should be a service_started, or a service_healthy
> services.web-assets-server.depends_on.fetch-and-convert-ubuntu-img.condition contains "service_completed_successfully", which is an invalid type, it should be a service_started, or a service_healthy
> services.registry.depends_on.generate-tls-certs.condition contains "service_completed_successfully", which is an invalid type, it should be a service_started, or a service_healthy

This was due to docker/compose#8154.

Signed-off-by: Manuel Mendez <[email protected]>

It is hard to tell when setup.sh is done in vagrant without having to
read/parse the output to figure out if we're at the last step. This change
makes it obvious. Its not so necessary for terraform but I'd like to keep
both scripts about as similar as possible.

Signed-off-by: Manuel Mendez <[email protected]>

cert is going away and was never really a good one anyway.

Signed-off-by: Manuel Mendez <[email protected]>

Don't need quotes for strings in yaml dicts (512M is a string due to the M)
and we definitely want them whenever they appear in a shell command.

Signed-off-by: Manuel Mendez <[email protected]>

To avoid confusion between the environment and cli params.

Signed-off-by: Manuel Mendez <[email protected]>

Added TINKERBELL_TLS (default false) since self-signed certs are going to
cause tink-worker to fail to connect.

Signed-off-by: Manuel Mendez <[email protected]>

These are no longer needed (some never were) so we lets drop them.

Signed-off-by: Manuel Mendez <[email protected]>

This way we can be sure that all the versions are kept in sync easily.

Signed-off-by: Manuel Mendez <[email protected]>

Lets make .env the central/source-of-truth for env configuration. This
means we don't have to deal with empty vars and default values all over the
docker-compose.yml file. This does not cause any change in treatment of
environment variables. Actual environment variables still supersede those set
in .env. The values in .env are thus just the default if left unspecified,
exactly like ${VAR:-default} in the docker-compose.yml file.

I also got rid of container configs that used the `environment` config to
inject the env vars so that the `command` can use it. Having the values
in the environment would only really be useful if we expect to `exec`
into the container and run some commands. I haven't needed to do that yet
so would rather avoid repetition until absoulutely necessary. We can just
have docker-compose inject the values directly into the `command` line.

Signed-off-by: Manuel Mendez <[email protected]>

${} isn't actually needed in any of these uses so lets just use the shorter form.

Signed-off-by: Manuel Mendez <[email protected]>

…nk-cli to hook

This way all the tink images are in sync and managed in just one place
(the .env file).

Signed-off-by: Manuel Mendez <[email protected]>

This has a bunch of linuxkit updates and more recent container images that have
dropped /cert support.

Signed-off-by: Manuel Mendez <[email protected]>