consul/test/integration/connect/envoy/case-ingress-mesh-gateways-resolver/secondary/setup.sh

#!/bin/bash

set -eEuo pipefail

register_services secondary

gen_envoy_bootstrap s1 19001 secondary
gen_envoy_bootstrap s2 19002 secondary
gen_envoy_bootstrap mesh-gateway 19003 secondary true
retry_default docker_consul secondary curl -s  "http://localhost:8500/v1/catalog/service/consul?dc=primary" >/dev/null
Allow ingress gateways to route through mesh gateways - Adds integration test for mesh gateways local + remote modes with ingress - ingress golden files updated for mesh gateway endpoints 2020-04-21 09:29:48 -05:00			`#!/bin/bash`

			`set -eEuo pipefail`

test: use direct service registration in envoy integration tests (#9138) This has the biggest impact on enterprise test cases that use namespaced registrations, which prior to this change sometimes failed the initial registration because the namespace was not yet created. 2020-11-09 13:59:46 -06:00			`register_services secondary`

Allow ingress gateways to route through mesh gateways - Adds integration test for mesh gateways local + remote modes with ingress - ingress golden files updated for mesh gateway endpoints 2020-04-21 09:29:48 -05:00			`gen_envoy_bootstrap s1 19001 secondary`
			`gen_envoy_bootstrap s2 19002 secondary`
			`gen_envoy_bootstrap mesh-gateway 19003 secondary true`
			`retry_default docker_consul secondary curl -s "http://localhost:8500/v1/catalog/service/consul?dc=primary" >/dev/null`