temporalio / temporalio/temporal
Schedules - allow TriggerImmediatelyRequest to define arguments
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
https://github.com/temporalio/api/blob/master/temporal/api/schedule/v1/message.proto#L278
Currently not possible to trigger schedule with a different payload than what is specified within the start action.
Ask is to allow arguments to be specified on trigger request
Use case - users wanting to trigger one-off schedule run with diff arguments than whats defined in start action
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 with temporal/api/schedule/v1/message.proto at line 278 and inspect TriggerImmediatelyRequest and the surrounding schedule messages. Trace where the trigger request is handled, then verify that a request can provide arguments different from the schedule's start action and that existing trigger behavior remains unchanged.
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