fission / fission-workflows

Workflows for Fission: Fast, reliable and lightweight function composition for serverless functions
Apache License 2.0
371 stars 42 forks source link

updating a workflow does not seem to work #239

Open grounded042 opened 5 years ago

grounded042 commented 5 years ago

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
    version: 1.0-rc2

k8s Version

v1.13.2

Commands Run

$ echo "apiVersion: 1
output: HelloWorld
tasks:
  HelloWorld:
    run: noop
    inputs: Hello, world" > hello-world.1.wf.yaml
$ echo "apiVersion: 1
output: HelloJon
tasks:
  HelloJon:
    run: noop
    inputs: Hello, Jon" > hello-world.2.wf.yaml
$ fission fn create --name hello-world --env workflow --src ./hello-world.1.wf.yaml
$ fission fn test --name hello-world
Hello, world
$ fission fn update --name hello-world --env workflow --src ./hello-world.2.wf.yaml
$ fission fn test --name hello-world
Hello, world

Expected Output

The last command should have output Hello, Jon corresponding to the workflow from the update command, but it instead has the workflow from the original workflow function creation command.

Other Notes

If you do a fission pkg info with the name of the package for the function it will display the updated function, however if you do a fission-workflows wf get on the workflow it seems to show the original workflow.