Skip to content

fix: wait for public e2e tunnel readiness - #116

Merged
fproulx-boostsecurity merged 1 commit into
mainfrom
fix/e2e-tunnel-readiness
Sep 17, 2026
Merged

fproulx-boostsecurity merged 1 commit into
mainfrom
fix/e2e-tunnel-readiness

Conversation

@fproulx-boostsecurity

Copy link
Copy Markdown
Contributor

Fresh Cloudflare quick tunnels can announce a hostname before public DNS serves it. The GOAT test could deploy a payload during that window, causing the first GitHub runner callback to fail with curl exit code 6.

This change waits for both local Kitchen health and the public tunnel health endpoint. It queries public DNS directly and pins the health request with curl --resolve to avoid stale NXDOMAIN entries in the host resolver cache. If a tunnel remains unreachable, E2E provisions a replacement and updates its runtime configuration before continuing.

Validation:

  • make e2e-goat - passed in 187 seconds through cache poisoning, GCP pivot, and flag capture
  • go test ./internal/rye
  • make -n e2e-up
  • git diff --check

@fproulx-boostsecurity
fproulx-boostsecurity merged commit 5103de5 into main Sep 17, 2026
4 checks passed
@fproulx-boostsecurity
fproulx-boostsecurity deleted the fix/e2e-tunnel-readiness branch September 17, 2026 20:25
@github-actions github-actions Bot locked and limited conversation to collaborators Sep 17, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants