localBatchFileScatter parse.inputs.json pointing to the wrong sample.batchfile.tsv file

[jayoung]

hey Amy,

I'm starting to look more closely at some actual wdl files to understand that end of things.

In testWorkflows/localBatchFileScatter, there is a local sample.batchfile.tsv file, but it's not being used.

The parse.inputs.json instead points to a copy of sample.batchfile.tsv here: /fh/fast/paguirigan_a/pub/ReferenceDataSets/workflow_testing_data/WDL/batchFileScatter /sample.batchfile.tsv, which uses files hosted on S3 rather than on /fh/fast

I think that's not what you intend - I'm guessing this workflow won't work for people who haven't got their AWS credentials set up: does that make sense?

Janet