You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment we have a Run Workflow option, which can be triggered from many places and is great.
When I have a file open, I want to be able to that step standalone. Probably just from the command palette - so we have Run Workflow and Run This Step or something.
In technical terms, we can either run the workflow and pass --only to just run this step file, or we can load the adaptor and credential etc from the workflow and run the expression standalone openfn job.js -a http -s input.json
The text was updated successfully, but these errors were encountered:
This is Mtuchi's biggest blocker now: he cannot run a single step (there is some confusion around this)
He uses --start, --end and --only in the CLI a lot.
Maybe what we need is "run this step" and "run workflow from this step" as two distinct commands? I think we can probably forgo "run between these steps" or "run until this step" for now. And actually I think the "only" has got to be the major use case. If it's easy to run one step with input, the dev can step through the workflow as they need and just run the bits they want
At the moment we have a Run Workflow option, which can be triggered from many places and is great.
When I have a file open, I want to be able to that step standalone. Probably just from the command palette - so we have
Run Workflow
andRun This Step
or something.In technical terms, we can either run the workflow and pass
--only
to just run this step file, or we can load the adaptor and credential etc from the workflow and run the expression standaloneopenfn job.js -a http -s input.json
The text was updated successfully, but these errors were encountered: