Skip to content

Feature/ngs360 workflow pin version - #185

Open
maggiecbms wants to merge 2 commits into
mainfrom
feature/ngs360_workflow_pin_version
Open

maggiecbms wants to merge 2 commits into
mainfrom
feature/ngs360_workflow_pin_version

Conversation

@maggiecbms

@maggiecbms maggiecbms commented Oct 26, 2026 •

Copy link
Copy Markdown
Collaborator

What

NGS360Platform.copy_workflow now returns <uuid>:<version> instead of the
bare workflow id, resolving the version the project is pinned to via
POST /projects/{id}/workflow-versions/{wf}/resolve (updated in NGS360/APIServer#474).

Why

A bare workflow id leaves WES to pick the version, and it picks the highest one by default.
A project's results then change silently whenever a new version is registered or
the prod alias moves. Resolving pins the version on first run and reuses it
after, so re-running months later submits the same version.

Explicit identifiers (<uuid>:3) pass through untouched — a one-off run against
a specific version must not change what the project uses from then on.

Tests

Six tests in tests/test_ngs360_ga4gh_platform.py cover first use, reuse after
the alias moves, explicit-version passthrough, the two raise paths, and that
task-reuse matching still works with the :version suffix.

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