openworkflowdev / openworkflowdev/openworkflow
Question: Custom runners for worker processes
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.3k
- Forks
- 66
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 69
Description
Hi there,
If one want to run OpenWorkflow workers on using custom runners / workers (e.g., GitHub Actions or Bitbucket Pipelines). The idea is to provision workers via our runner APIs and have them poll the DB. Is this a supported pattern, or are workers expected to be long-running processes that the open workflow services host itself?
If it's supported, any guidance on best practices for short-lived/ephemeral runners vs. long-lived workers would be appreciated.
Thanks!
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
The issue names no files, tests, or entry points. First determine whether runner APIs support ephemeral and long-lived workers, then document the supported pattern and best practices for GitHub Actions or similar custom runners.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- backend, devops
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100