@bsmithgall The CLI command used a config file which I haven't accounted for yet, so #56 will fail the build test. I was thinking of parsing the config file within the scripts code and then sending them as individual arguments to the pipeline. Maybe along the lines of moving the pipeline.set_config_from_file() code to pipeline.scripts and then writing a new function in pipeline to handle a dict of arbitrary settings?
Or.... now that I type this all out, maybe it would make more sense to keep a lot of the old config file stuff in pipeline, but rework it a bit so that using a file is optional. I think I'll close #56 and try that.
@bsmithgall The CLI command used a config file which I haven't accounted for yet, so #56 will fail the build test. I was thinking of parsing the config file within the scripts code and then sending them as individual arguments to the pipeline. Maybe along the lines of moving the
pipeline.set_config_from_file()code topipeline.scriptsand then writing a new function inpipelineto handle adictof arbitrary settings?Or.... now that I type this all out, maybe it would make more sense to keep a lot of the old config file stuff in pipeline, but rework it a bit so that using a file is optional. I think I'll close #56 and try that.