chore(stovepipe): rearrange stovepipe files into gateway subdirectory#181
Merged
Conversation
Move example client/server from example/{client,server}/stovepipe to
example/stovepipe/gateway/{client,server} with compose and Dockerfile aligned
to main SubmitQueue examples. Relocate stovepipe RPC code under
stovepipe/gateway (rename proto to gateway.proto, add yarpc output). Add
stovepipe/entity and stovepipe/extension package anchors, core/extension stub,
and Makefile targets for Stovepipe gateway Linux builds, queue-only schema init,
and local compose using STOVEPIPE_LOCAL_PROJECT. Integration tests target the
new gateway compose path; root gateway/orchestrator protopb unchanged from main.
34cd28e to
7eab09c
Compare
behinddwalls
approved these changes
Jun 2, 2026
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.
We had initially set up a single stovepipe service, but we will actually use a similar model to submitqueue and have a gateway + orchestrator that can be deployed separately. This change shifts existing stovepipe files into the gateway and updates code references throughout.
After, I will add a stovepipe orchestrator and we can proceed to gradually rearrange the existing submitqueue files into this layout.
Why?
We're planning on the intended layout below, to better manage submitqueue + stovepipe as separate projects that have some shared dependencies but distinct deployability. This is an initial step toward getting to the layout below:
What?
Move files into gateway and move into directories
Test Plan
make local-stovepipe-gateway-startIssue