Every time you run a Disdat pipeline, Disdat tracks the code used to produce the data, the task's parameters, and the input bundles. This command gives you access to that information.
First, let's say we've run the following pipeline from our disdat-examples repo.
$dsdt apply pipelines.dependent_tasks.B...===== LuigiExecutionSummary=====Scheduled3tasksofwhich:* 3 ran successfully:-1A(...)-1B(...)-1DriverTask(...)Thisprogresslooks:) because there were no failed tasks or missing dependencies===== LuigiExecutionSummary=====