Clarify whether nested output directories are permitted about remote-apis HOT 4 CLOSED

Anything not explicitly disallowed is allowed:

Output directory/file is child of another output directory: allowed.
Output directory is child of output file: not possible and will not work, because then the output file is not actually file, which will cause a FAILED_PRECONDITION error. If we expect an output to be a symlink to a directory, it should be specified as an output directory, not an output file.

from remote-apis.

... and perhaps it's worth it to clarify this point in the proto :-)
Will do.

from remote-apis.

Output directory is child of output file: not possible and will not work, because then the output file is not actually file, which will cause a FAILED_PRECONDITION error. If we expect an output to be a symlink to a directory, it should be specified as an output directory, not an output file.

Does this mean that execution servers that preserve symlinks need to test the type of the symlink target? I was previously assuming symlinks were uploaded as-is. If the server is expected to validate the target also, can you add a comment for that?

from remote-apis.

If the server is expected to validate the target also, can you add a comment for that?

Done. (#74)
Also, in general I would like to remove the explicit type specification of outputs by the client in V3 (#75).

from remote-apis.