Extra column for 'list' specifying the input JSON

[kvg]

While developing new workflows, I often run one workflow per sample. Checking on the status of each sample is currently a bit painful because if a workflow fails, I need to dig through the metadata to figure out which sample it was.

For example, while trying to analyze four test samples and then running cromshell list -u -c, I get this:

DATE CROMWELL_SERVER RUN_ID WDL_NAME STATUS 20190929_231921 https://cromwell-v45.dsde-methods.broadinstitute.org eb5d37a7-b518-4cff-be8f-2ce8655881a4 NanoporeRNA.wdl Running 20190929_231946 https://cromwell-v45.dsde-methods.broadinstitute.org c35da98c-b8e9-40bf-9670-afab75a9bc5b NanoporeRNA.wdl Failed 20190929_231959 https://cromwell-v45.dsde-methods.broadinstitute.org e626c920-838b-4917-9582-3e42cffcbc03 NanoporeRNA.wdl Succeeded 20190929_232029 https://cromwell-v45.dsde-methods.broadinstitute.org 179fb6fd-71d8-4b16-8fbc-7252a8897969 NanoporeRNA.wdl Succeeded

My goal is to see at a glance which workflow specifically failed, but the current status list does not immediately tie a workflow to the input I ran it with. I currently run cromshell metadata on the particular RUN_ID and then work out from the metadata which sample I must be looking at.

Instead, I'd love to see another column here that tells me what I supplied as the input JSON (which I generally name things like SampleA.json, SampleB.json, etc.). That way, I'd know exactly which sample was completed, still running, or had failed without having to look anything else up.

Since the table is already pretty wide, adding a column may overflow the line, and that wouldn't look very nice. But I'd be happy to not see the CROMWELL_SERVER column anymore; I typically don't care about that column in my day-to-day work.

[jonn-smith]

@kvg Yeah - I've thought about this as well.

Right now there's a faster way to do it than polling the metadata - the JSON and WDL files are stored in your ~/.cromshell/<SERVER>/<UUID>/` folder, so you can take a look at them there.