cloudflared-mirror/component-tests/constants.py

METRICS_PORT = 51000
MAX_RETRIES = 5
BACKOFF_SECS = 7
MAX_LOG_LINES = 50

PROXY_DNS_PORT = 9053
MANAGEMENT_HOST_NAME = "https://management.argotunnel.com"


def protocols():
    return ["http2", "quic"]
TUN-4049: Add component tests to assert logging behavior when running from terminal 2021-03-08 15:42:49 +00:00			`METRICS_PORT = 51000`
TUN-4052: Add component tests to assert service mode behavior 2021-03-12 13:37:53 +00:00			`MAX_RETRIES = 5`
			`BACKOFF_SECS = 7`
TUN-6741: ICMP proxy tries to listen on specific IPv4 & IPv6 when possible If it cannot determine the correct interface IP, it will fallback to all interfaces. This commit also introduces the icmpv4-src and icmpv6-src flags 2022-09-20 10:39:51 +00:00			`MAX_LOG_LINES = 50`
TUN-4851: Component tests to sanity check that Proxy DNS and Tunnel are only run when expected 2021-07-30 16:44:11 +00:00
			`PROXY_DNS_PORT = 9053`
TUN-7360: Add Get Host Details handler in management service With the management tunnels work, we allow calls to our edge service using an access JWT provided by Tunnelstore. Given a connector ID, this request is then proxied to the appropriate Cloudflare Tunnel. This PR takes advantage of this flow and adds a new host_details endpoint. Calls to this endpoint will result in cloudflared gathering some details about the host: hostname (os.hostname()) and ip address (localAddr in a dial). Note that the mini spec lists 4 alternatives and this picks alternative 3 because: 1. Ease of implementation: This is quick and non-intrusive to any of our code path. We expect to change how connection tracking works and regardless of the direction we take, it may be easy to keep, morph or throw this away. 2. The cloudflared part of this round trip takes some time with a hostname call and a dial. But note that this is off the critical path and not an API that will be exercised often. 2023-04-18 08:59:55 +00:00			`MANAGEMENT_HOST_NAME = "https://management.argotunnel.com"`
TUN-5600: Add coverage to component tests for various transports This parameterizes relevant component tests by transport protocol where applicable. The motivation is to have coverage for (graceful or not) shutdown that was broken in QUIC. That logic (as well as reconnect) is different depending on the transport, so we should have it parameterized. In fact, the test is failing for QUIC (and passing for others) right now, which is expected until we roll out some edge fixes for QUIC. So we could have caught this earlier on. 2022-01-04 19:20:43 +00:00

			`def protocols():`
TUN-7245: Add bastion flag to origin service check 2023-03-06 23:19:10 +00:00			`return ["http2", "quic"]`