Add ContextPropagators option for replay tests #1019
Merged
Conversation
This file contains 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.
What was changed
This PR enables setting
ContextPropagatorson workflow replay options, which can currently only be set onclient.Optionspassed to a worker.Why?
Context propagators can extract information from workflow headers and modify workflow contexts. This is important for workflow replay in some cases, because information in a
workflow.Contextmay be used to modify workflow behavior, eg. workflow code that performs role based access control based on claims in workflow headers.Checklist
How was this tested:
This was tested in our internal environment where workflow replay was previously failing due to missing context propagators.