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

Provide input parameters via command line in single workflow/"run" mode. #3406

Open
danbills opened this issue Mar 14, 2018 · 1 comment
Open

Comments

@danbills
Copy link
Contributor

per this forum discussion, user would find it easier to provide inputs via CLI than inputs.json.

@duartemolha
Copy link

as an addition to this ... it would be better if you could provide SOME inputs via CLI and the remaining in a inputs.json file (with the CLI inputs taking precedence over the same inputs (if they exist) in the inputs file.

An example if this that I would like to use is for example, if you have a workflow that does a whole bunch of processed to a pair of fastq files...

It would be great if you could still provide an inputs.jsob with all of the required inputs and just over-ride the 2 fastq file inputs with the CLI arguments

@gemmalam gemmalam added the Needs Triage Ticket needs further investigation and refinement prior to moving to milestones label Nov 5, 2018
@rebrown1395 rebrown1395 added Feature Request and removed Needs Triage Ticket needs further investigation and refinement prior to moving to milestones labels Dec 5, 2018
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

4 participants