Support input from parameters not only output artifacts (orig: How to get output parameters from output file instead of stdout?)

[argoproj-labs]

Support input from parameters not only output artifacts (orig: How to get output parameters from output file instead of stdout?)

[flaviuvadan]

Ah, got it, so this is a feature enhancement we need to do: support input from parameters not only output artifacts!

[MichaelLan]

Hello, at the moment I have created a wrapper for the Task class, for now it's working for me, I would like work in this feature, but I don't know if internally they are already working on it.

In this comment you can see my implementation, still under construction.
#138 (comment)

[flaviuvadan]

Hello @xiang9156! Yes, one can use input/output artifacts for passing files between tasks. Here's an example 🙂 In that example the writer writes a file to a specific path, which is listed as an OutputArtifact, then the consumer reads that file, which is listed as an InputArtifact.

[flaviuvadan]

Closing this issue as I am pretty confident this is supported and the example showcases how to take advantage of the feature! Feel free to reopen if the answer was not clear 🙂

[RunningIkkyu]

@flaviuvadan Could we provide a way to parse json from artifact output directly without starting a new task?

[xiang9156]

Hello @xiang9156! Yes, one can use input/output artifacts for passing files between tasks. Here's an example 🙂 In that example the writer writes a file to a specific path, which is listed as an OutputArtifact, then the consumer reads that file, which is listed as an InputArtifact.

Thank you @flaviuvadan for the reply. Right now we are using the output parameters instead of artifacts, so that we can refer the json parameter like this "{{=jsonpath(tasks['entry'].outputs.parameters.result, '$.result.job_id')}}" , I checked the examples you shared, looks like it needs a middle layer to read the output artifact and print it to stdout.