fission-workflows

fission-workflows copied to clipboard

Currently workflows are defined using a backward dependencies. For example: ```yaml myTask: ... requires: otherDepTask1: ~ otherDepTask2: ~ ``` While provides more self-contained tasks, for simple use cases it might...

erwinvaneyk

Feature request: allow single-stepping through workflows while being able to inspect task inputs and outputs.

soamvasani

- Incorporate Fission's FunctionRef into workflow engine

erwinvaneyk

Benchmark tool

1

In order to account for some of the requirements of this project: performance, scalability, reliability. A simple benchmark is needed. As the workflow engine is not different from any other...

erwinvaneyk

Infinite Recursion Detection

2

Given that a major emphasis is made on re-using workflows and recursion over iteration. It is vital for the workflow engine to have some sort of recursion detection. **Solution 1**...

erwinvaneyk

Allow users to dynamically add internal functions

2

Currently internal functions (like if, noop and sleep) are hardcoded into the workflow engine, though they are built to be extensible. A user should be able to add internal functions...

erwinvaneyk

Currently only internal functions can be dynamic tasks (tasks that return a task). Support should be added to the fission runtime environment to also allow fission functions to be dynamic...

erwinvaneyk

There used to be (in the JSON format) support to force the type of an input. This functionality should also be supported in the YAML format.

erwinvaneyk

Already partly supported, but needs to be fleshed out.

erwinvaneyk

Let's use this issue to keep track of workflow visualization. We also want to implement a GUI editor for workflows. There's enough in common between these two efforts that we...

soamvasani