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

#!/bin/bash

set -euo pipefail

# wait for service registration
wait_for_agent_service_register s1
wait_for_agent_service_register s2
wait_for_agent_service_register s2-v1

# force s2-v1 into a warning state
set_ttl_check_state service:s2-v1 warn

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

gen_envoy_bootstrap s1 19000
gen_envoy_bootstrap s2 19001
gen_envoy_bootstrap s2-v1 19002
connect: rework how the service resolver subset OnlyPassing flag works (#6173) The main change is that we no longer filter service instances by health, preferring instead to render all results down into EDS endpoints in envoy and merely label the endpoints as HEALTHY or UNHEALTHY. When OnlyPassing is set to true we will force consul checks in a 'warning' state to render as UNHEALTHY in envoy. Fixes #6171 2019-07-23 20:20:24 -05:00			`#!/bin/bash`

			`set -euo pipefail`

			`# wait for service registration`
			`wait_for_agent_service_register s1`
			`wait_for_agent_service_register s2`
			`wait_for_agent_service_register s2-v1`

			`# force s2-v1 into a warning state`
			`set_ttl_check_state service:s2-v1 warn`

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

			`gen_envoy_bootstrap s1 19000`
			`gen_envoy_bootstrap s2 19001`
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-v1 19002`