consul/test/integration/connect/envoy/case-cross-peer-control-pla.../primary/setup.sh

#!/bin/bash

set -euo pipefail

upsert_config_entry primary '
kind = "proxy-defaults"
name = "global"
config {
  protocol = "tcp"
}
'
upsert_config_entry primary '
kind = "mesh"
peering {
  peer_through_mesh_gateways = true
}
'

register_services primary

gen_envoy_bootstrap s1 19000 primary
gen_envoy_bootstrap mesh-gateway 19001 primary true
Add integ test for peering through gateways 2022-10-10 19:55:28 +00:00			`#!/bin/bash`

			`set -euo pipefail`

test: fix envoy integration tests to explicitly create config entries (#15269) This is instead of the current behavior where we feed the config entries in using the config_entries.bootstrap configuration which oddly races against other setup code in some circumstances. I converted ALL tests to explicitly create config entries. 2022-11-07 16:02:04 +00:00			`upsert_config_entry primary '`
			`kind = "proxy-defaults"`
			`name = "global"`
			`config {`
			`protocol = "tcp"`
			`}`
			`'`
			`upsert_config_entry primary '`
			`kind = "mesh"`
			`peering {`
			`peer_through_mesh_gateways = true`
			`}`
			`'`

Add integ test for peering through gateways 2022-10-10 19:55:28 +00:00			`register_services primary`

			`gen_envoy_bootstrap s1 19000 primary`
			`gen_envoy_bootstrap mesh-gateway 19001 primary true`