Should we allow triggers to point to multiple jobs?
Open
Nobody has claimed this yet.
question
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
- As a user that has a webapp that sends data TO OpenFn, I may only be able to configure one webhook url.
- In order to split that webhook trigger into multiple paths for my various forms, I need to first add a single job linked to the trigger, then add multiple downstream jobs with various filter conditions on their paths.
- This first job is unnecessary and I often build it as a
fn(state => state)no-op job.
Contributor guide
No contributing guide indexed for this repository
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 locating how webhook triggers link to jobs, then trace how downstream paths and their filter conditions are represented. Done should mean a webhook trigger can route directly to multiple jobs, removing the need for an intermediate no-op job.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100