Output files configurable download location (e.g., to the local machine; to a bucket; etc.)

[arpita0911patel]

Is your feature request related to a problem? Please describe.
Need to enhance the HelloNGEN.sh script so that the location of the output files is configurable. They could get downloaded on the user's local machine if needed; or perhaps directed into a bucket, etc..

Describe the solution you'd like
Either in the realization file (requires upstream changes) or in some portion of the docker/wrapper script and wrapper configuration, include an option for the output location that is flexible and configurable. Optimally, the solution will have flexibility to be incorporated at a more upstream point when resources are available to make that change.

Describe alternatives you've considered
The alternative would be to go ahead and make the upstream change. We should touch base with the ngen team to see if this is underway.

Additional context
... coming soon...

[arpita0911patel]

@benlee0423

[benlee0423]

@ZacharyWills Are you currently working on it? If not, I will work on this. Let me know.

[benlee0423]

@ZacharyWills @arpita0911patel
Any copy command after ngen command in HelloNGEN.sh might not run.
I did very simple experiment how files are copied to host machine with entrypoint execution.
I created the following run.sh file,

#!/bin/bash
echo prehello > /ngen/data/prehello.txt
/echo-hello
echo hello > /ngen/data/hello.txt

And run this as entrypoint in Dockerfile

...
ENTRYPOINT [ "/run.sh"]

Run the image with the command

docker run --rm -it -v /Users/benjaminlee/data:/ngen/data <<IMAGE_ID>>

In my host machine, I am seeing prehello.txt file, but not hello.txt.

benjaminlee$ pwd
/Users/benjaminlee/data
benjaminlee$ ls
prehello.txt

So, in recent commit, putting copy command inside ngen command should work. I will run this locally.