search

ga4gh / task-execution-schemas

Apache License 2.0
82 stars 29 forks source link

DockerExecutor.{stdout,stderr} should imply entries in Task.outputs, automatically #15

Closed buchanae closed 7 years ago

buchanae commented 7 years ago

Currently, if you want to capture stdout/stderr for a task, you need to define paths under DockerExecutor and then also create a TaskParameter for those paths and add those to the Task record. This seems redundant and could be simplified by expecting a TES server to infer the stdout/stderr TaskParameter records automatically.

buchanae commented 7 years ago

After discussion outside of this thread, the consensus was that this is a small problem for a small number of people who are implementing a TES client/server. The existing spec is low-level, flexible, and powerful. It's not worth adding complexity to the spec in order to save a few lines of code for client/server implementors.

Going to close this issue, but feel free to comment and/or reopen if I'm getting hasty.