I have been trying to use postman runner from last year for this feature but looks like no one has reported this as a issue nor a feature request.
But for our use case, it’s a must to have, as we want to upload to our REST APIs a non-json, non-csv file which gets executed at a later point of workflow.
Thanks for your response. I did go through that issue however the issue there talks about a valid JSON file however in our case we have a tool which we want to upload and then the tool will later be used.
This tool is not a JSON or csv but an unix executable file in gatk format.
This file runs in a container for further execution and results.
Here is some more screenshot to describe the problem. Unfortunately, I cannot share the request details further.
We have a form-data with file-type as input and wanted to pass that as part of the runner so that the execution takes that as an input file for one of the REST API we are testing in the flow.
I’m currently away at the moment and I still don’t fully understand what you are trying to do within the runner.
You might be able put the file in the Postman working directory and use it that way but I’m not near my machine so I couldn’t tell you if that works or not.
You may need to raise a formal feature request on our GH Issue tracker containing the full details of the request. That way we can triage the request appropriately.