When this happens, we actually execute step b before a,. Removing something before executing a will remove the output generated by b.
Second, it is unclear when to remove the files since the output files can be valid and need to be validated by signature. We will need to remove output files right before the statements are executed (after signature validation), then we have steps executor, substep executor etc, and task executor. This is doable but certainly not an easy task.
This looks like a reasonable feature, but there are a few problems.
First as described in #1496, nested workflows can cause problems:
When this happens, we actually execute step
bbeforea,. Removingsomethingbefore executingawill remove the output generated byb.Second, it is unclear when to remove the files since the output files can be valid and need to be validated by signature. We will need to remove output files right before the statements are executed (after signature validation), then we have steps executor, substep executor etc, and task executor. This is doable but certainly not an easy task.