Passing variables with query params

[nsheff]

Wouldn't it be cool if you could pass variables through query params to adjust attributes in the PEP?

For example, say a PEP has a derived column that uses an environment variable like $DATA, because the files are stored in $DATA/subfolder/{sample_name}.fq, or something.

If when you hit the endpoint to get some file attribute, you could pass /endpoint?DATA=/my/local/path, then the server could return a path that was useful for your local environment.

[nsheff]

This is (still) a good idea!

[nsheff]

Hey @nleroy917 I think this is going to be an important thing to focus on now.

[nsheff]

There are 3 types of path:

• absolute: /path/to/data.xyz
• relative: to/data.xyz
• dynamic: $MYDATA/data.xyz

[nsheff]

If derived attributes could access project attributes, and not just sample attributes as is currently the case... and if there was a way to modify project attributes on-the-fly....

then dynamic paths could provide a universal solution, I think.

[nsheff]

@nleroy917 can you comment on the status of this issue?

[nleroy917]

Nothing has been implemented... but this is just for fetching a project, correct? I.e. /projects/{namespace}/{project} it will "fill in" the env variables as the PEP is fetched?

[nsheff]

Nothing has been implemented... but this is just for fetching a project, correct? I.e. /projects/{namespace}/{project} it will "fill in" the env variables as the PEP is fetched?

yes.

[nleroy917]

A potential solution: https://stackoverflow.com/questions/2059482/temporarily-modify-the-current-processs-environment

It was discussed that we could only include this option for specific endpoints (like a POST to /api/v1/projects/{namespace}/{project} )