Skip to content

Commit e496020

Browse files
kenahrensclaude
andcommitted
Add --test-against localhost:8080 to proxymock replay commands
The pulled traffic was recorded from Kubernetes where the service was called outerspace-server:8080. When replaying in CI, we need to redirect these requests to localhost:8080 where the service actually runs. This fixes the "generator run failed: readiness checks: tcp probe against outerspace-server:8080: unable to connect" error. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
1 parent 7fe78c2 commit e496020

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

Makefile

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ integration-test: build proxymock-mock
4040
echo "Waiting for outerspace-go to start..."
4141
sleep 2
4242
echo "Running integration tests with proxymock..."
43-
proxymock replay --in $(PROXYMOCK_RECORDING) --fail-if requests.response-pct!=100
43+
proxymock replay --in $(PROXYMOCK_RECORDING) --test-against localhost:8080 --fail-if requests.response-pct!=100
4444
echo "Cleaning up..."
4545
-pkill -f "outerspace-go" || true
4646
-pkill -f "proxymock" || true
@@ -53,7 +53,7 @@ load-test: build proxymock-mock
5353
echo "Waiting for outerspace-go to start..."
5454
sleep 2
5555
echo "Running load tests with proxymock..."
56-
proxymock replay --in $(PROXYMOCK_RECORDING) --no-out --vus 10 --for 1m --fail-if "latency.p95 > 200"
56+
proxymock replay --in $(PROXYMOCK_RECORDING) --test-against localhost:8080 --no-out --vus 10 --for 1m --fail-if "latency.p95 > 200"
5757
echo "Cleaning up..."
5858
-pkill -f "outerspace-go" || true
5959
-pkill -f "proxymock" || true

0 commit comments

Comments
 (0)