clarifies documentation so state that all input files and directories will be mounted as read-only.
Since the mounted paths of inputs and outputs are explicitly provided, we do not need to duplicate this information in the Volume message. The same is true regarding the working dir.
Requested free disk space is now part of Resources. It didn't make much sense where it was before.
The volumes field in the Task message refers to locations in the Executors where data may be written, but is not explicitly an output directory. One could use this to share temporary data between Executor steps.
kellrott
commented
7 years ago
This PR:
Since the mounted paths of inputs and outputs are explicitly provided, we do not need to duplicate this information in the Volume message. The same is true regarding the working dir.
Requested free disk space is now part of Resources. It didn't make much sense where it was before.
The volumes field in the Task message refers to locations in the Executors where data may be written, but is not explicitly an output directory. One could use this to share temporary data between Executor steps.