Repository navigation
Replies: 1 comment
|
Coming in a bit late. You might be able to get around this problem by using the |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I have trouble understanding what the right and most elegant way is to write to an input directory in Google Cloud.
Example of a process that computes the reference sizes:
Output working directory contents are (
gsutil ls -r gs://BUCKET/workdir):The original reference directory does not get updated:
Adding:
to the process definition does not do anything.
The only way to manage doing this is by publishing to the input directory, however I cannot pass the input directory to the publishDir directive as is as when I am using
pathvariable, the input directory is actually the mounted softlink and not the actual GS location, so the only way is to pass an extra argument to the process withvalinstead ofpathlike so:Maybe it is my OCD, but this way is ugly, unmaintainable, and the programmer should have experience to use it. There is no documentation about this bug and workaround. So I have to ask fellow developers, what am I missing here? Thank you all for your answers in advance!
All reactions