Project

General

Profile

Actions

Bug #16208

closed

Workbench2 doesn't show inputs then #main object is not a Workflow

Added by Lucas Di Pentima almost 5 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
Normal
Assigned To:
-
Category:
Workbench2
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
-
Release relationship:
Auto

Description

Individual CWL steps don't have a cwl.input.json file to display. However, we can have arvados-cwl-runner to put cwl input contents into the same cwl.input.json mount point that is used for workflows. However, unlike workflows, changing the contents of cwl.input.json and re-running the step would not have any effect, because the parameters have already been baked into the command line and mount points.

Somewhat related, we should have a convention for identifying intermediate output collections, so that they can be more easily filtered, selected, and trashed.


Related issues 1 (1 open0 closed)

Related to Arvados Epics - Story #16945: WB2 Workflows / containers feature parityIn Progress08/01/202103/31/2023

Actions
Actions #1

Updated by Peter Amstutz almost 5 years ago

  • Target version deleted (2020-03-11 Sprint)
  • Release set to 31
Actions #2

Updated by Peter Amstutz almost 5 years ago

  • Description updated (diff)
Actions #3

Updated by Lucas Di Pentima over 4 years ago

  • Assigned To deleted (Lucas Di Pentima)
Actions #4

Updated by Peter Amstutz almost 4 years ago

  • Related to Story #16945: WB2 Workflows / containers feature parity added
Actions #5

Updated by Peter Amstutz over 2 years ago

  • Description updated (diff)
Actions #6

Updated by Peter Amstutz about 2 years ago

  • Status changed from New to Closed
Actions

Also available in: Atom PDF