Skip to content

feat(echo): the status route - #27

Merged
rennf93 merged 1 commit into
masterfrom
feat/status-route
Oct 8, 2026
Merged

rennf93 merged 1 commit into
masterfrom
feat/status-route

Conversation

@rennf93

@rennf93 rennf93 commented Oct 8, 2026 •

Copy link
Copy Markdown
Member

What

Ports fastapi-guard guard/status.py add_status_route onto the echo adapter - the echo-column MISSING row (FEATURE_MATRIX_GO section 2, GAP 16; nethttp has had the pattern since 1.3.x).

How

  • NewStatusHandler(engine) serves the engine's initialization status JSON: the cloud-provider table (ready / last_refreshed / entries per provider, mirroring cloud_handler.get_status), the geo handler's get_status snapshot or null (the reference getattr fallback dance), and the redis component (enabled + a live PTTL probe: disabled reports ok=true, a probe failure reports ok=false with the redacted error).
  • AddStatusRoute(app, engine, path) registers it at DefaultStatusPath (/_guard/status) or a custom path; GET only; nil engine/app rejected.
  • Same payload shape and probe key grammar as the nethttp sibling.

Gates

  • gofmt, go vet, staticcheck clean; unit + integration suites green against local redis; the 100% coverage gate green (100.0%)

Ports fastapi-guard guard/status.py add_status_route onto the echo
adapter (the nethttp sibling's seam): NewStatusHandler serves the
engine's initialization status JSON (cloud_providers table with ready /
last_refreshed / entries rows, the geo handler's get_status snapshot or
null, and the redis component with a live PTTL probe), and
AddStatusRoute registers it on the echo instance at DefaultStatusPath or
a custom path. GET only; a nil engine or app is rejected.
@rennf93 rennf93 added the no-issue Chore or dependency PR that does not need an issue label Oct 8, 2026
@github-actions github-actions Bot added the tests Test suite changes label Oct 8, 2026
@rennf93
rennf93 merged commit fb72f9d into master Oct 8, 2026
14 of 15 checks passed
@rennf93
rennf93 deleted the feat/status-route branch October 8, 2026 01:03
rennf93 added a commit that referenced this pull request Oct 9, 2026
… lifecycle surface - floor guard-core-go v4.3.2 (#30)

The family 1.4.0 wave on Echo: GuardWebSocket plus WebSocketHTTPStatus
(#26), AddStatusRoute (#27), the adapter lifecycle surface (MarkInitialized,
GetInitializationStatus, Reset, AgentStats, RefreshCloudIPRanges, #28).
Raises the engine floor to v4.3.2, pins golang.org/x/net v0.60.0 for the
five 2026 http2 GO advisories reachable through the cloud-refresh
lifecycle, and carries the post-transfer Guard-Core metadata sweep.

Co-authored-by: Renn F <rennf93@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-issue Chore or dependency PR that does not need an issue tests Test suite changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant