Using FH cluster paths during API tests

[tefirman]

For WDL's that require the use of FH paths in their inputs (#2, #17, #39), we need a way to obfuscate those paths in the repo while adding them back in during submission via the API GitHub Action.

One approach that might work is one similar to the filter_response_bodies function in conftest.py but in reverse.

For instance, in the input json, we use some sort of keyword like PATH_ROOT, and then during submission within the API tests, we replace PATH_ROOT with the specified path. Wondering if this would overcomplicate things though..

[seankross]

• We need to create these sensitive paths at runtime from github environmental variables.
• We may want to check for sensitive paths before merging into main + what to do if you find one.

[sckott]

@tefirman is going to ask @sitapriyamoorthi if a relative path can be used instead of absolute. if not, then we'll go with path replacement

[sckott]

@tefirman let me know when you get an answer on this

[sitapriyamoorthi]

Well theoretically you would have to expose the parent directory somewhere. So you could theoretically never completely hide the path? Unless we hide all paths in some hidden json file and just tell in the public facing readme to get this unit test to work you need to have the these files in some locations

[sckott]

@tefirman and I talked about this. I think the next step is that Taylor is updating the PR #129 with relative paths so we don't have to redact any paths, and then seeing if that works as a solution - if memory serves?

[tefirman]

Correct, I've got a PR into this branch with potential updates, but still debugging one API check: #183

[sckott]

thanks @tefirman

[sckott]

@tefirman where are we at on this?