Details
-
Type:
Story
-
Status: Won't Fix
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: pipe_base, pipe_tasks
-
Labels:None
-
Story Points:6
-
Epic Link:
-
Team:Data Release Production
Description
All CmdLineTask invocations should record their input and output data IDs in their metadata, as well as any relevant information about why any user-provided data ID was not used and/or produced.
This will require an audit of all CmdLineTasks that are used in the BatchPoolTasks in pipe_drivers. It should not involve any framework-level code (in e.g. pipe_base), unless that code significantly simplifies the per-CmdLineTask work.
Attachments
Activity
I think this got put in a new epic only because of a cycle-rollover script Yusra AlSayyad runs. I'm closing it as Won't Fix.
I'm not entirely sure how this ticket has been assigned to a fall 2022 epic. It seems to be entirely gen2 and we should be able to close it as Won't Fix. Jim Bosch do you want to rebrand the ticket as a gen3 provenance ticket? By "metadata" do you mean dataIDs written to the files as described in DM-35396?