DongHyeonkaandClaude Opus 5
5f10b791d3
Snapshot of the in-flight state that already existed, identically, in both this worktree and the main checkout before this session began: the initial HTTP Client platform implementation (previously untracked), the redis-lab removal, and the JPA / object-storage / notification integration work. Kept separate from this session's HTTP Client review response, which lands in the following commit, so the two bodies of work stay reviewable apart. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
18 lines
652 B
YAML
18 lines
652 B
YAML
# Fault-injection topology for the HTTP Client Platform failure suite (design §28.1, §28.3).
|
|
#
|
|
# The suite normally drives Toxiproxy through Testcontainers. This compose file exists for the
|
|
# nightly lane and for reproducing a failure locally with the exact same image and ports.
|
|
services:
|
|
toxiproxy:
|
|
image: ghcr.io/shopify/toxiproxy:2.9.0
|
|
container_name: httpclient-toxiproxy
|
|
ports:
|
|
- "8474:8474" # control API
|
|
- "18080:18080" # proxied upstream: plaintext
|
|
- "18443:18443" # proxied upstream: TLS
|
|
healthcheck:
|
|
test: ["CMD", "/toxiproxy-cli", "list"]
|
|
interval: 5s
|
|
timeout: 3s
|
|
retries: 10
|