[CRE] Sharding support in HTTP gateway handler - #23400
Draft
bolekk wants to merge 1 commit into
Draft
Conversation
Contributor
|
✅ No conflicts with other open PRs targeting |
Contributor
|
I see you updated files related to
|
|
mchain0
reviewed
Aug 13, 2026
mchain0
reviewed
Aug 13, 2026
bolekk
force-pushed
the
http_shards
branch
3 times, most recently
from
August 18, 2026 03:10
607dc04 to
a82a9d3
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
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.




HTTP Trigger now understands workflows assigned to multiple shards (e.g. primary + backup). Workflow registration is handled per-shard. Incoming trigger requests are routed to all shards the workflow is assigned to.
HTTP action doesn't need any shard-related changes.
Two main files changed by the PR: