Remove non-code directories about long-read-pipelines HOT 6 CLOSED

Maybe we should move all the input JSONs to a separate private repo?

from long-read-pipelines.

That'd be great.

Although, I feel like we are tacking a bigger problem, that Terra is trying solve:
how do you nicely connect code and input/specification, yet keep them separately maintained?

from long-read-pipelines.

But it's not an easy task to make modifications to the workflow now in Terra, per my understanding.
So I'd vote for what you suggested, move the data and reports dir to some other place with appropriate access control.

from long-read-pipelines.

Yeah, though we will need to leave workflow test JSONs behind. Having a test JSON for a workflow you're importing seems to be a Dockstore requirement.

from long-read-pipelines.

I'd say that's not a bad requirement (well there are multiple aspects of this), in the sense that at least there's a test (assuming it doesn't give a false sense of security).

And it is not conflicting with #7.

from long-read-pipelines.

Done. This codebase now only contains workflow code and test specifications, and is suitable for any group (inside and outside the Broad) to use. The production input JSONs are now in a separate repo.

from long-read-pipelines.