Add Intermediate-Context header support for Talaria message metadata #558
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
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.
This PR introduces the
intermediate-contextheader as an optional field in the metadata preparation flow for both online and offline messages sent by Talaria.Purpose: The
intermediate-contextheader allows for carrying any extra information that may be required by the receiving systems.Note: The addition of the
intermediate-contextheader in Talaria depends on corresponding updates in webpa-common. A PR has been raised for those changes: xmidt-org/webpa-common#1160.Once the webpa-common PR is merged, Talaria’s go.mod file should be updated to reference the new tag. After that, this Talaria MR can be merged.