Launchpad user role is too restrictive
acknowledged
C
Charcoal Mandrill
The current
Launch
user role permissions in Seqera Platform is problematic due to two key restrictions that the role applies (due to the inability to adjust the "Pipeline Settings" during pipeline launching). These are:- the need to change Git revision (so users can compare results from different pipeline versions)
- the need to submit pipeline run using a params JSON instead of the Platform user interface
Both of these have ended up being critical deficiencies in the
Launch
user role. It's become a basic requirement for even the most simple usages that all Platform users need to be able to modulate the version (Git revision) of the pipeline they are running.Also, considering the sheer number of input parameters for many pipelines from nf-core (I think the nf-core
rnaseq
pipeline has ~60 input parameters) the usage of the Platform Launchpad UI to manually "click-ops" through the selection of a large set of custom parameters is not feasible. Even the most basic users end up needing to resort to using the params JSON for pipeline submission, both due to the size and complexity of the input pipeline params, but also for record-keeping so that they don't have to manually click ~60+ buttons in a UI every time they want to submit a Run with a given input params setup.
Rob Newman
acknowledged