Before, users had to manually parse yaml's to semi-unreadable json's before submitting the function. This is annoying and seems to cause some confusing for new users.
This PR resolves these issues, by automating the parsing/transformation step using a Fission Builder. The user can create a workflow simply using the yaml workflow definition as the source. This source is passed to a Fission Builder for Fission Workflows, which generates the corresponding json.
This PR will make Fission Workflows depend on any Fission version which includes this https://github.com/fission/fission/pull/397 -- which contains some related bug fixes in Fission.
Flyby:
Updated the deploy script
removed code/examples/references pointing to json-based workflows
Removed '.yaml' extension requirement from wfcli
Changed wfcli parse <file> to output generated json over stdout.
Before, users had to manually parse yaml's to semi-unreadable json's before submitting the function. This is annoying and seems to cause some confusing for new users.
This PR resolves these issues, by automating the parsing/transformation step using a Fission Builder. The user can create a workflow simply using the yaml workflow definition as the source. This source is passed to a Fission Builder for Fission Workflows, which generates the corresponding json.
This PR will make Fission Workflows depend on any Fission version which includes this https://github.com/fission/fission/pull/397 -- which contains some related bug fixes in Fission.
Flyby:
wfcli parse <file>to output generated json over stdout.Fixes #60 #28 #72