Argv to workflow in run
Reported by bahuvrihi | March 2nd, 2009 @ 04:39 PM
Static workflows are great, but they need a way to receive arguments. One option is to hack into the schema, only allow one file in run and then tack on the args:
% tap run workflow.yml a b c
Another option is to implement a workflow task:
% tap run -- workflow workflow.yml a b c
(wap?) Which then makes a pass-through workflow and enques the inputs to node 0, and completes to the result of node -1. The workflow task would be a baseclass for more complicated pass-through workflows. You could make a generator that takes a workflow.yml as an input and builds a stub workflow task!
Comments and changes to this ticket
-
bahuvrihi May 3rd, 2009 @ 08:55 AM
With the new schema setup... perhaps add something to parse:
% tap run -spath --@0 one two threeWhere the @key adds to queue.
-
bahuvrihi May 25th, 2009 @ 12:07 PM
- Assigned user set to “bahuvrihi”
- State changed from “new” to “invalid”
There are better ways to do this, for example using load and a redirection.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
A framework for making configurable, file-based tasks and workflows.
bahuvrihi