mirror of
https://github.com/status-im/consul.git
synced 2025-01-11 14:24:39 +00:00
9f656a2dc8
* Make exec test assert Envoy version - it was not rebuilding before and so often ran against wrong version. This makes 1.10 fail consistenty. * Switch Envoy exec to use a named pipe rather than FD magic since Envoy 1.10 doesn't support that. * Refactor to use an internal shim command for piping the bootstrap through. * Fmt. So sad that vscode golang fails so often these days. * go mod tidy * revert go mod tidy changes * Revert "ignore consul-exec tests until fixed (#5986)" This reverts commit 683262a6869033cb79e68fa1dba0f9ea83e9187d. * Review cleanups
17 lines
730 B
Bash
17 lines
730 B
Bash
#!/bin/bash
|
|
|
|
set -euo pipefail
|
|
|
|
# Force rebuild of the exec container since this doesn't happen if only the
|
|
# version argument changed which means we end up testing the wrong version of
|
|
# Envoy.
|
|
docker-compose build s1-sidecar-proxy-consul-exec
|
|
|
|
# Bring up s1 and it's proxy as well because the check that it has a cert causes
|
|
# a proxy connection to be opened and having the backend not be available seems
|
|
# to cause Envoy to fail non-deterministically in CI (rarely on local machine).
|
|
# It might be related to this know issue
|
|
# https://github.com/envoyproxy/envoy/issues/2800 where TcpProxy will error if
|
|
# the backend is down sometimes part way through the handshake.
|
|
export REQUIRED_SERVICES="s1 s1-sidecar-proxy-consul-exec"
|