temporalio / temporalio/temporal
Header propagation on activity/workflow results
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Is your feature request related to a problem? Please describe.
On our Temporal projects we use context propagators to pass cross-cutting parameters across the "temporal stack", i.e. the user that is running a workflow etc.
This works fine, anyway a use case arised where we need to set/change some of these variables within an activity (but it may be also within a workflow) and have it "propagated" when the result of the activity is returned to the calling workflow.
Describe the solution you'd like
We would like to be able to change contxt propagated vars within activity/workflow. Please refer also to https://community.temporal.io/t/context-propagator-java-sdk/2189/6?u=andreacolombo
Describe alternatives you've considered
None.
Additional context
None.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reviewing how context propagators currently move values across the Temporal stack, especially between activities and calling workflows; done should define and verify how changes made in an activity or workflow propagate back with the activity result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100