Currently there are two ways to launch a pipeline via the API:
  • Populate the body of a POST
    /workflow/launch
    request, which requires getting a number of details such as the compute environment and configuration
  • Create an action and POST
    /actions/${actionId}/launch
    , which only take pipeline params as options
It would be nicer to reconcile the two and have a simpler flow:
  • Create pipeline on Seqera Platform
  • Launch specified pipeline using an endpoint, e.g. POST
    /pipeline/${pipelineId}/launch
Importantly you would only be able to modify a very limited subset of options with this option, e.g. the pipeline parameters. This would save the automation developer the time and effort in writing a number of requests to GET settings before launching a pipeline via automation. The revision, compute environment, working directory, staging options and many other settings would be fixed and require addition of a new pipeline for a launch.
This has some overlap with some other feature requests such as: