Replies: 1 comment
-
you can point argument of your task to workflow input like this An example that is closely matching your case you can find in the tests, e.g. here |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
@djarecka - I am attempting to implement the worker from the PSI/J site, which consists of two parts: 1. Extracting text from a PDF (
pdftotext INPUT.pdf OUTPUT.txt
) and 2. Creating a word cloud image from the extracted text (wordcloud_cli --text OUTPUT.txt --imagefile IMAGE.png
).My approach involves creating
ShellCommandTasks
for the above commands and adding them to the workflow to execute them. Here is my working code:One observation I made is that it is necessary to provide the
input_spec
andset_output
to the workflow. In the given code, I provided a dummyinput_spec
because I only wanted to execute static shell commands where the filenames were already defined in theargs
parameter. However, let's say I do want to provide my PDF filename as input to the workflow. In that case, how can I use it as a 'Lazy Input' for myshelly1
task?Beta Was this translation helpful? Give feedback.
All reactions