temporalio / temporalio/temporal
Support opt-in ability to get workflow input and output (if closed) on describe workflow
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Describe the solution you'd like
Some users need workflow input/output without crawling history. This is something that is being added for Nexus operations and standalone activities. We should add for workflows too.
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
Start by tracing the existing DescribeWorkflow entry point and review how workflow descriptions currently expose state. Then compare the planned workflow support with the existing Nexus operation and standalone activity input/output handling; done means an opt-in way to retrieve workflow input and output, including for closed workflows, without crawling history.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend-api-design, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100