Create proposal on how to abstract the workflow Runner definition #559
Labels
area/documentation
Related to all activities around documentation
area/engine
Relates to Engine
enhancement
New feature or request
needs-triage
Relates to issues that should be refined
Description
Currently, we are hard-coded to the Argo Workflows, which is our only built-in runner. As a result, we are also tight to Kubernetes. This is against our decision of making Capact generic. We should create abstracted workflow definition which can be implemented by others. Maybe we can do it base on already existing spec, e.g. https://serverlessworkflow.io/
Additionally, we need to figure out how to extract and share the common logic between different runners (e.g. Interface resolution).
Reason
Make Capact platform-agnostic - enable implementing Engine for other platforms.
Use cases
The text was updated successfully, but these errors were encountered: