feat(stovepipe): add start controller for the change ingress flow#229
Draft
mnoah1 wants to merge 2 commits into
Draft
feat(stovepipe): add start controller for the change ingress flow#229mnoah1 wants to merge 2 commits into
mnoah1 wants to merge 2 commits into
Conversation
…key packages Move the shared queue consumer framework to top-level core/consumer so both SubmitQueue and Stovepipe can reuse it. Pipeline stage constants now live in per-domain submitqueue/core/topickey and stovepipe/core/topickey packages.
Stovepipe gateway -> start -> validate skeleton:
- ChangeEvent: single-commit, source-agnostic ingress payload
({"uri": "git://owner/repo/branch/revision"}) published to the start topic
by the webhook/poller.
- start controller deserializes the ChangeEvent, derives the owner/repo
partition key so a repo's commits stay ordered, and publishes a thin
ChangeURI reference to the validate topic (publish-only until validate lands).
- stovepipe/entity/git parses git:// commit identities into a ChangeID,
domain-scoped like submitqueue's github/phabricator ChangeID parsers.
Deferred to follow-up PRs once their consumers exist: orchestrator commit
storage, the gateway status/log sinks, and lifting the cross-domain change
identity into the shared entity package (a SubmitQueue refactor unrelated to
this flow).
mnoah1
force-pushed
the
mnoah1/stovepipe-start-controller
branch
from
424e438 to
5ca558a
Compare
gsturges
approved these changes
Jun 9, 2026
mnoah1
force-pushed
the
mnoah1/lift-core-consumer
branch
from
2a53a64 to
425f060
Compare
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
2 participants
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.
Stovepipe gateway -> start -> validate skeleton:
Deferred to follow-up PRs once their consumers exist: orchestrator commit storage, the gateway status/log sinks, and lifting the cross-domain change identity into the shared entity package (a SubmitQueue refactor unrelated to this flow).
Why?
What?
Test Plan
Issue