consul/test/integration/connect/envoy/defaults.sh

#!/bin/bash

export DEFAULT_REQUIRED_SERVICES="s1 s1-sidecar-proxy s2 s2-sidecar-proxy"
export REQUIRED_SERVICES="${DEFAULT_REQUIRED_SERVICES}"
export REQUIRE_SECONDARY=0
export REQUIRE_PARTITIONS=0
export REQUIRE_PEERS=0
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			`#!/bin/bash`

			`export DEFAULT_REQUIRED_SERVICES="s1 s1-sidecar-proxy s2 s2-sidecar-proxy"`
			`export REQUIRED_SERVICES="${DEFAULT_REQUIRED_SERVICES}"`
Add cross-partition integration test 2021-11-12 14:45:50 -07:00			`export REQUIRE_SECONDARY=0`
peering: mesh gateways are required for cross-peer service mesh communication (#13410) Require use of mesh gateways in order for service mesh data plane traffic to flow between peers. This also adds plumbing for envoy integration tests involving peers, and one starter peering test. 2022-06-09 11:05:18 -05:00			`export REQUIRE_PARTITIONS=0`
			`export REQUIRE_PEERS=0`