Skip to content

fix: warn instead of crash when operator events topics configured without sink#835

Merged
alexluong merged 3 commits intomainfrom
fix/opevents-sink-no-crash
Apr 14, 2026
Merged

fix: warn instead of crash when operator events topics configured without sink#835
alexluong merged 3 commits intomainfrom
fix/opevents-sink-no-crash

Conversation

@alexluong
Copy link
Copy Markdown
Collaborator

Summary

  • When opevents.Topics are configured but no sink is set, the server previously crashed on startup with a fatal error
  • Now logs a warning via slog.Warn and returns a NoopSink, allowing the server to start gracefully (operator events will be dropped)
  • Only internal/opevents/config.go is changed

Test plan

  • Start Outpost with topics configured but no sink — verify it starts and logs a warning instead of crashing
  • Start Outpost with topics + a valid sink — verify normal behavior is unchanged
  • Start Outpost with no topics and no sink — verify NoopSink returned with no warning

🤖 Generated with Claude Code

…hout sink

When topics are configured but no sink is set, the server would crash on
startup with a fatal error. Instead, log a warning and return a NoopSink
so the server can start gracefully (operator events will be dropped).

Co-Authored-By: Claude <noreply@anthropic.com>
@vercel
Copy link
Copy Markdown

vercel bot commented Apr 14, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
outpost-docs Ready Ready Preview, Comment Apr 14, 2026 8:21pm
outpost-website Ready Ready Preview, Comment Apr 14, 2026 8:21pm

Request Review

Replace stdlib log/slog with the project's *logging.Logger for
consistency. NewSink now accepts a logger parameter, and callers in
builder.go pass b.logger.

Co-Authored-By: Claude <noreply@anthropic.com>
@alexluong alexluong merged commit 2cd13e3 into main Apr 14, 2026
4 checks passed
@alexluong alexluong deleted the fix/opevents-sink-no-crash branch April 14, 2026 20:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants