Open BlakeMScurr opened 6 years ago
Specifically, if I write a workflow that uses a fission function with a dash - in it, such as:
-
apiVersion: 1 output: Hello tasks: InternalFuncKickOff: run: noop Hello: run: hello-go inputs: "{$.Invocation.Inputs.default}" requires: - InternalFuncKickOff
then testing that workflow will hang, and the workflow pod in the fission-function namespace will indefinitely log:
time="2018-05-10T23:25:43Z" level=error msg="Workflow is not ready yet." wf.status=PENDING
the hello-go function works fine on its own.
It would be nice to get an immediate error when deploying these workflows malformed, or at least when running them.
Versions: Workflows: 0.2.0 Fission: 0.6.0 Kubernetes:1.10.2
Specifically, if I write a workflow that uses a fission function with a dash
-
in it, such as:then testing that workflow will hang, and the workflow pod in the fission-function namespace will indefinitely log:
the hello-go function works fine on its own.
It would be nice to get an immediate error when deploying these workflows malformed, or at least when running them.
Versions: Workflows: 0.2.0 Fission: 0.6.0 Kubernetes:1.10.2