feat(hook): Deliver events to integrations - #607
Merged
Merged
Conversation
1 task
prathshenoy
force-pushed
the
prath.shenoy/hook-event-contract
branch
from
August 17, 2026 16:54
b5394eb to
837e0d8
Compare
prathshenoy
force-pushed
the
prath.shenoy/hook-dispatch
branch
from
August 17, 2026 16:56
a09dcab to
b6aef89
Compare
prathshenoy
marked this pull request as ready for review
August 17, 2026 16:56
prathshenoy
requested review from
a team,
behinddwalls and
sbalabanov
as code owners
August 17, 2026 16:56
prathshenoy
force-pushed
the
prath.shenoy/hook-event-contract
branch
from
August 18, 2026 00:27
837e0d8 to
b5394eb
Compare
prathshenoy
force-pushed
the
prath.shenoy/hook-dispatch
branch
from
August 18, 2026 00:27
b6aef89 to
a09dcab
Compare
1 task
Collaborator
|
🛑 Automatic stack rebase aborted — diff mismatch The rebase of Please rebase manually and verify the changes are correct. |
mnoah1
reviewed
Aug 19, 2026
behinddwalls
pushed a commit
to behinddwalls/submitqueue
that referenced
this pull request
Aug 19, 2026
## Summary **What**: - Define the shared event format every domain publishes for fire-and-forget lifecycle notifications, carrying origin, type, timing, a staleness marker, and open per-event detail. - Derive an event's identity from the transition it describes, so replaying a transition produces the same identity and duplicate deliveries collapse. **Why**: - Enable integrations to react to pipeline milestones without adding call sites that can stall or fail a merge. - Establish one schema and one identity rule before any producer ships, so a consumer spanning several domains needs only one reader. ## Test Plan - [x] Add unit tests. ## Revert Plan - Revert this PR. No topic is registered and no message of this shape exists on any queue. ## Issues - [CODEM-416](https://linear.app/uber/issue/CODEM-416/hooks-integration-downstream-notificaiton) ## Stack 1. @ uber#606 1. uber#607 1. uber#608
behinddwalls
previously requested changes
Aug 19, 2026
prathshenoy
force-pushed
the
prath.shenoy/hook-dispatch
branch
from
August 20, 2026 20:54
a09dcab to
56a21ac
Compare
An error occurred while trying to automatically change base from
prath.shenoy/hook-event-contract
to
main
August 20, 2026 20:58
An error occurred while trying to automatically change base from
prath.shenoy/hook-event-contract
to
main
August 20, 2026 20:58
An error occurred while trying to automatically change base from
prath.shenoy/hook-event-contract
to
main
August 20, 2026 20:58
An error occurred while trying to automatically change base from
prath.shenoy/hook-event-contract
to
main
August 20, 2026 20:58
prathshenoy
force-pushed
the
prath.shenoy/hook-dispatch
branch
from
August 20, 2026 20:59
56a21ac to
63b4e01
Compare
prathshenoy
changed the base branch from
prath.shenoy/hook-event-contract
to
main
August 20, 2026 21:36
prathshenoy
marked this pull request as draft
August 20, 2026 22:13
prathshenoy
force-pushed
the
prath.shenoy/hook-dispatch
branch
from
August 24, 2026 16:36
63b4e01 to
8503587
Compare
prathshenoy
marked this pull request as ready for review
August 24, 2026 16:53
prathshenoy
force-pushed
the
prath.shenoy/hook-dispatch
branch
from
August 24, 2026 17:20
8503587 to
07e57cc
Compare
prathshenoy
enabled auto-merge
August 24, 2026 17:59
1 task
mnoah1
approved these changes
Aug 24, 2026
prathshenoy
force-pushed
the
prath.shenoy/hook-dispatch
branch
from
August 24, 2026 19:33
07e57cc to
e297c9d
Compare
prathshenoy
force-pushed
the
prath.shenoy/hook-dispatch
branch
from
August 24, 2026 19:35
e297c9d to
e08c06b
Compare
prathshenoy
temporarily deployed
to
stack-rebase
August 24, 2026 19:40 — with
GitHub Actions
Inactive
behinddwalls
pushed a commit
to behinddwalls/submitqueue
that referenced
this pull request
Sep 25, 2026
## Summary **What**: - Register the orchestrator's hook stage, so lifecycle events are consumed from the queue and handed to the integrations each event resolves to. No integration is wired yet, so events are accepted and discarded. - Register the matching dead-letter stage, so an event that fails every retry is recorded and alerted on instead of accumulating unread. **Why**: - Prove the delivery path end to end before anything produces an event, so a later change adds producers to a route that already works. - Keep a deployment with no integrations configured distinguishable from one that is silently losing events. ## Test Plan - [x] Add unit tests. ## Revert Plan - Revert this PR. Since nothing publishes hook events yet and the resolver returns only a no-op hook, no side effect is lost. ## Issues - [CODEM-416](https://linear.app/uber/issue/CODEM-416/hooks-integration-downstream-notificaiton) ## Stack 1. uber#607 1. @ uber#608 1. uber#632
behinddwalls
pushed a commit
to behinddwalls/submitqueue
that referenced
this pull request
Sep 25, 2026
## Summary **What**: - Register the hook stage and its dead-letter stage in Stovepipe's consumer wiring, on a topic named for the domain, with a resolver that hands every event to the no-op hook. **Why**: - Wire the stage in a second domain, so attaching a real integration to Stovepipe is a resolver swap rather than new plumbing, and two domains on one queue backend keep their own hook topics. ## Test Plan - [x] Add unit tests. ## Revert Plan - Revert this PR. Nothing publishes hook events yet and the resolver returns only a no-op hook. ## Issues - [CODEM-416](https://linear.app/uber/issue/CODEM-416/hooks-integration-downstream-notificaiton) ## Stack 1. uber#607 1. uber#608 1. @ uber#632
This branch was previously deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
What:
Why:
Test Plan
Revert Plan
Issues