fission-workflows
fission-workflows copied to clipboard
Workflows for Fission: Fast, reliable and lightweight function composition for serverless functions
The fission controller proxy for the workflows apiserver doesn't work if workflows is installed in a different namespace from the fission controller. ``` $ wfcli status panic: unknown error (status...
I have a workflow with a nested `foreach`. The workflow passes validation, the following call does not return any output: ```sh fission wf validate nested.wf.yaml ``` Creating the workflow works:...
https://github.com/fission/fission-workflows/blob/master/Docs/functions.md#repeat > A complete example of this function can be found in the repeatwhale example. repeatwhale points to `https://github.com/fission/fission-workflows/blob/master/examples/whales/repeatwhale.wf.yaml` which doesn't exist
The currently implemented event store was written with a limited knowledge of NATS streaming, abusing some of the features. Currently the naieve setup consists of the following subject structure -...
## Fission / Workflows Version ``` $ fission -v client: fission/core: gitcommit: 045ab734c6bd04cdc07ebd80f05874c7122ffd18 builddate: 2018-12-13T07:56:27Z version: 1.0-rc1 workflows: gitcommit: "" builddate: "" version: 0.6.0 server: fission/core: gitcommit: 12f6d91224c95e9e60da4adddd9922a273ace060 builddate: 2019-01-14T17:02:51Z...
## Fission / Workflows Version ``` $ fission -v client: fission/core: gitcommit: 045ab734c6bd04cdc07ebd80f05874c7122ffd18 builddate: 2018-12-13T07:56:27Z version: 1.0-rc1 workflows: gitcommit: "" builddate: "" version: 0.6.0 server: fission/core: gitcommit: 12f6d91224c95e9e60da4adddd9922a273ace060 builddate: 2019-01-14T17:02:51Z...
Expanding upon #239: the current e2e test suite only uses the minimal functions to deploy and execute Fission functions; many features are not explicitly covered by the tests To ensure...
Nested functions can be confusing and unclear to a new user. For example I wanted to run a `if` check on the output of a `foreach` - so I try...
Currently `fission workflows invocation get` (listing workflow invocations) lists all workflow invocations, which after some production workloads can quickly add up. Since the command does a GET on each workflow...
As an intermediate step towards the `proxy` executor, one step that we already can take is to move the workflow engine to the `newdeploy` executor. The `newdeploy` executor aligns much...