Bug #17286

Print workbench URL for submitted CR

Added by Peter Amstutz 9 months ago. Updated 6 months ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
CWL
Target version:
Start date:
01/22/2021
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
Story points:
-
Release relationship:
Auto

Description

arvados-cwl-runner logs the UUID of the container request but it would be more convenient if it also printed a clickable URL to workbench so that smart terminals like gnome terminal or vscode terminal can take you directly to the workflow page.


Subtasks

Task #17288: Review 17286-print-urlsResolvedLucas Di Pentima

Associated revisions

Revision 75efbc85
Added by Peter Amstutz 9 months ago

Merge branch '17286-print-urls' refs #17286

Arvados-DCO-1.1-Signed-off-by: Peter Amstutz <>

History

#1 Updated by Peter Amstutz 9 months ago

  • Assigned To set to Peter Amstutz
  • Status changed from New to In Progress
  • Description updated (diff)

#3 Updated by Lucas Di Pentima 9 months ago

I've just a couple of concerns:

  • When no workbenches are set up this would output a confusing message.
  • I think this isn't taking into account when the user submits a runner to a federated cluster.

Other than that, it LGTM.

#4 Updated by Peter Amstutz 9 months ago

Lucas Di Pentima wrote:

I've just a couple of concerns:

  • When no workbenches are set up this would output a confusing message.

The messages all either fall back or don't print if neither workbench2 or workbench1 is defined.

  • I think this isn't taking into account when the user submits a runner to a federated cluster.

I guess it is technically possible that the user could send the workflow runner to a different cluster, but currently nobody does that. If that was a thing, ideally we would have federation features that let you visit the local workbench and it would fetch the remote container request for you.

Other than that, it LGTM.

#6 Updated by Lucas Di Pentima 9 months ago

LGTM, thanks!

#7 Updated by Peter Amstutz 9 months ago

  • Status changed from In Progress to Resolved

#8 Updated by Peter Amstutz 6 months ago

  • Release set to 38

Also available in: Atom PDF