Bug #17286
closed
Print workbench URL for submitted CR
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.
Updated by Peter Amstutz almost 4 years ago
- Assigned To set to Peter Amstutz
- Status changed from New to In Progress
- Description updated (diff)
Updated by Peter Amstutz almost 4 years ago
17286-print-urls @ 7c99875efea3ec5415427063cf79ddc44c58f55f
Updated by Lucas Di Pentima almost 4 years 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.
Updated by Peter Amstutz almost 4 years 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.
Updated by Peter Amstutz almost 4 years ago
17286-print-urls @ 714cc9a889786a062641f3627d557667cc71c337
Updated by Peter Amstutz almost 4 years ago
- Status changed from In Progress to Resolved