consul/test/integration/connect/envoy/case-cfg-resolver-defaultsubset/setup.sh

#!/bin/bash

set -euo pipefail

# wait for bootstrap to apply config entries
wait_for_config_entry proxy-defaults global
wait_for_config_entry service-resolver s2

# s2 is retained just to have a honeypot for bad envoy configs to route into
gen_envoy_bootstrap s1 19000
gen_envoy_bootstrap s2-v1 19001
gen_envoy_bootstrap s2-v2 19002
gen_envoy_bootstrap s2 19003
tests: adding new envoy integration tests for L7 service-resolvers (#6129) Additionally: - wait for bootstrap config entries to be applied - run the verify container in the host's PID namespace so we can kill envoys without mounting the docker socket * assert that we actually send HEALTHY and UNHEALTHY endpoints down in EDS during failover 2019-07-23 20:08:36 -05:00			`#!/bin/bash`

			`set -euo pipefail`

			`# wait for bootstrap to apply config entries`
			`wait_for_config_entry proxy-defaults global`
			`wait_for_config_entry service-resolver s2`

			`# s2 is retained just to have a honeypot for bad envoy configs to route into`
			`gen_envoy_bootstrap s1 19000`
			`gen_envoy_bootstrap s2-v1 19001`
			`gen_envoy_bootstrap s2-v2 19002`
Envoy Mesh Gateway integration tests (#6187) * Allow setting the mesh gateway mode for an upstream in config files * Add envoy integration test for mesh gateways This necessitated many supporting changes in most of the other test cases. Add remote mode mesh gateways integration test 2019-07-24 17:01:42 -04:00			`gen_envoy_bootstrap s2 19003`