Skip to content

feat(router): add event relays administration page - #321

Closed
JohnChantz wants to merge 7 commits into
ui-rewritefrom
feat/event-relays
Closed

feat(router): add event relays administration page#321
JohnChantz wants to merge 7 commits into
ui-rewritefrom
feat/event-relays

Conversation

@JohnChantz

@JohnChantz JohnChantz commented Sep 4, 2026

Copy link
Copy Markdown
Collaborator

What kind of change does this PR introduce? (check at least one)

  • Bugfix
  • Feature
  • Code style update
  • Refactor
  • Build-related changes
  • Other, please describe:

Does this PR introduce a breaking change? (check one)

  • Yes
  • No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

  • It's submitted to the master branch
  • When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx, where "xxx" is the issue number)

If adding a new feature, the PR's description includes:

  • A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

Summary

  • Adds an Admin Event Relays page at /router/event-relays so operators can create, edit, disable, and delete mappings from exact bus events to ReBAC-protected socket rooms.
  • Includes local template preview (sample JSON → resolved resource + rendered payload) before save, plus list search and a sockets-disabled warning.
  • Companion backend: feat(router): add ReBAC-protected event-to-socket relays Conduit#1588

Test plan

  • Open /router/event-relays against a Router that includes the event-relays Admin API
  • Empty state → New relay → local preview → create
  • Edit, disable (active), delete, and search
  • Confirm the sockets-off warning when Router sockets are disabled
  • pnpm test:event-relays

Give operators CRUD for mapping exact bus events to ReBAC-protected
socket rooms, with a local template preview before save.
Subscribe to MongoDB change streams through a short-lived admin socket
ticket so operators can see pending updates without auto-refreshing the
grid.
The Database module returns the index list itself, so reading
result.indexes threw on the model settings tab.
Give schema settings JS, Postman, and Admin snippets so developers can
subscribe to change events without guessing the handshake. Deduplicate
resume tokens so reconnects do not inflate the pending-update count.
Keep both branches' package.json test scripts: event-relays, realtime, and schema-fields.
Give operators an in-page guide so they can tell relays from queues
and wire a bus event to permission-scoped socket subscribers.
@JohnChantz

Copy link
Copy Markdown
Collaborator Author

Split into two independent PRs for review:

The original feat/event-relays branch is unchanged.

@JohnChantz JohnChantz closed this Sep 11, 2026
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.

1 participant