Add deployment id to firehose connection headers #5319
Merged
Conversation
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
2 tasks
leoyvens
approved these changes
Apr 5, 2024
sduchesneau
pushed a commit
to streamingfast/substreams
that referenced
this pull request
Apr 6, 2024
for better integration since graph-node is now passing the deployment id when connecting to Substream endpoints, see here: graphprotocol/graph-node#5319
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.
Fixes #5098
When running firehose infrastructure it helps to know which subgraph is consuming substreams modules that are failing.
This PR makes it possible by adding deployment id to firehose/substreams request via
x-deployment-idheader