[Feature Request] Support not following runs with `temporal workflow execute`
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 379
- Forks
- 103
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 23
Description
Is your feature request related to a problem? Please describe.
If a workflow continues as new (or is otherwise part of a chain?), a user reports that temporal workflow execute doesn't give the first run's result.
Describe the solution you'd like
Add a flag for this use case, something like --dont-follow-runs.
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 temporal workflow execute command and how it follows a workflow chain. Determine the intended flag behavior for workflows that continue as new, then add coverage showing that the command can either follow runs or stop at the initial run and report its result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100