Skip to content

SET-1313 analysis runner seqera cli - #781

Draft
dancoates wants to merge 1 commit into
mainfrom
SET-1313-analysis-runner-seqera-cli
Draft

dancoates wants to merge 1 commit into
mainfrom
SET-1313-analysis-runner-seqera-cli

Conversation

@dancoates

Copy link
Copy Markdown
Contributor

This generally aligns more closely with seqera cli's tw launch than with existing analysis-runner conventions.
https://docs.seqera.io/platform-cli/reference/launch

Though there is some analysis-runner logic applied - or at least scaffolded to be applied in the server side implementation.

  • Rather than specifying compute env and workspace, you specify dataset and access level, and the server will look up the compute env and workspace from those.
  • Overriding of config with local config is disallowed for access levels other than test. This is because some config fields could be used to execute arbitrary code on the workflow runner. For access levels standard/full, a config can be specified but it must abide by the same rules as the workflow itself, ie. being on the main branch of an allow-listed repository.
  • Several other tw launch args are omitted as we don't have a clear use case yet, they can be added later if needed.

@dancoates
dancoates requested a review from jmarshall September 18, 2026 06:47
@dancoates
dancoates requested a review from a team as a code owner September 18, 2026 06:47
This generally aligns more closely with seqera cli's `tw launch` than
with existing analysis-runner conventions.
https://docs.seqera.io/platform-cli/reference/launch

Though there is some analysis-runner logic applied - or at least
scaffolded to be applied in the server side implementation.

- Rather than specifying compute env and workspace, you specify dataset
  and access level, and the server will look up the compute env and
  workspace from those.
- Overriding of config with local config is disallowed for access levels
  other than test. This is because some config fields could be used to
  execute arbitrary code on the workflow runner. For access levels
  standard/full, a config can be specified but it must abide by the same
  rules as the workflow itself, ie. being on the main branch of an
  allow-listed repository.
- Several other `tw launch` args are omitted as we don't have a clear
  use case yet, they can be added later if needed.
@dancoates
dancoates force-pushed the SET-1313-analysis-runner-seqera-cli branch from efd650c to 1e7473e Compare September 18, 2026 06:49
@dancoates
dancoates marked this pull request as draft September 18, 2026 06:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant