Feature #14016

[API] Container request can provide existing collection UUID that will accept CR output

Added by Peter Amstutz 4 months ago. Updated 4 months ago.

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

0%

Estimated time:
Story points:
-

Description

In order to set properties on the output of a container request, we need a way to set those properties on the collection that will become the output of the container request. Currently, that collection doesn't exist until the container request is finalized.

There are fields output_name and output_ttl which specify metadta on the output collection. It is a slippery slope if we keep adding fields (output_properties, output_storage_class, output_owner_uuid, ???)

A more flexible option is to embed the whole record in a jsonb field.

An even more flexible option is to add the option for the submitter to provide a collection UUID that will be the output collection of the container request.

Semantics:

  1. Caller creates the collection ahead of time and sets desired fields (such as name, properties)
  2. On CR submission and then again on CR completion, test that the user has writable permission to the collection record
  3. On finalize, copy the manifest_text/portable_data_hash of the container output collection to the collection in output_uuid

Related issues

Related to Arvados - Story #11942: [CWL] arvados-cwl-runner should support tagging output collection using propertiesIn Progress2017-07-05

History

#1 Updated by Peter Amstutz 4 months ago

  • Status changed from New to In Progress

#2 Updated by Peter Amstutz 4 months ago

  • Description updated (diff)

#3 Updated by Peter Amstutz 4 months ago

  • Status changed from In Progress to New

#4 Updated by Tom Morris 4 months ago

  • Related to Story #11942: [CWL] arvados-cwl-runner should support tagging output collection using properties added

Also available in: Atom PDF