tower-cli
tower-cli copied to clipboard
[Bug] The nexflow config field is not inherited correctly when changing Compute Environment
There is a mismatch between launches from the UI and the CLI when trying to launch a pipeline using a different compute environment than the one stored with the pipeline.
Minimal example
- Create a CE "CE1" and set something in the nextflow config field (Staging option)
- Create a second CE "CE2" and set a different text for the nextflow config field.
- Create a pipeline and associate "CE1" to it.
- Do not edit the nextflow config field so that it is inherited by the CE.
- In the UI, launch the pipeline selecting "CE2" as Compute Environment
- From the CLI do the same
tw launch -c CE2 <pipeline> - Check the two runs
- The run launched from the UI will have the nextflow config field correctly populated with the value from "CE2"
- The run launched via the CLI will have the nextflow config field correctly populated with the value from "CE1"
Expected behavior
- The run launched via the CLI will have the nextflow config field correctly populated with the value from "CE12