Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dynamic_variables_command_template needs a relative key #276

Closed
nsheff opened this issue Jun 25, 2020 · 1 comment
Closed

dynamic_variables_command_template needs a relative key #276

nsheff opened this issue Jun 25, 2020 · 1 comment
Assignees

Comments

@nsheff
Copy link
Contributor

nsheff commented Jun 25, 2020

If I want to include a python script in dynamic_variables_command_template, right now I have to either hard code the path in the pipeline interface, or execute looper from within a particular folder where that script exists.

Instead, this should operate the same with the command_template does, with some key specifying a path that's relative to the pipeline interface file.

@stolarczyk
Copy link
Member

stolarczyk commented Jul 2, 2020

works this way:

pipeline_name: refgenie
pipeline_type: sample
input_schema: refgenie_build.yaml
compute:
  dynamic_variables_script_path: build-compute-params.py # path, absolute or relative to the pipeline interface file
  dynamic_variables_command_template: >
    {pipeline.compute.dynamic_variables_script_path} -a {sample.asset}
...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants