Crate eggress_cli

Modules§

ProcessExit: Typed process outcome. Prefer returning this from command handlers and converting to a numeric code once at the process boundary over threading raw i32 constants through business logic.

EXIT_BIND_FAILURE
EXIT_CLI_PARSE_ERROR
EXIT_CONFIG_VALIDATION
EXIT_EXTERNAL_DEPENDENCY
EXIT_PLATFORM_MISSING
EXIT_RUNTIME_FAILURE
EXIT_SIGINT
EXIT_SIGTERM
EXIT_SUCCESS: Stable process exit codes shared by the eggress and pproxy binaries. This module is the single owner of the numeric process contract; the eggress-cli crate re-exports these constants instead of defining its own overlapping copies.
EXIT_UNSUPPORTED_FEATURE

build_test_chain_executor: Build the upstream-test chain executor from the production connector registry (eggress-server::build_chain_executor), not a CLI-local reimplementation.
exit_code_name
parse_pproxy_test_target: Parse the URL-shaped pproxy --test value into the target address used by the shared native upstream tester. The regular eggress upstream test command continues to accept its existing host:port form.
print_upstream_test_result
run_async_test
run_upstream_test: Run upstream tests against a compiled config and return the exit code.
run_upstream_test_with_mode: Run upstream tests with an explicit mode (“proxy” or “tcp”).
runtime_error_exit_code: Map a runtime startup/serve error to its process exit code.
test_upstream_tcp