Details
-
Type:
Bug
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: ap_verify
-
Labels:None
-
Story Points:5
-
Epic Link:
-
Sprint:AP S21-2 (January), AP S21-3 (February)
-
Team:Alert Production
-
Urgent?:No
Description
Attempting to rerun ap_verify twice in the same location gives the following error:
ValueError: Output run 'ap_verify-output' already exists, but --extend-run was not given.
|
Reconfigure ap_verify to use current pipetask idioms.
See DMTN-167, as updated by RFC-741, for a discussion of how --output, --output-run, and --extend-run were meant to be used.
Per
DM-18715, should also allow for config changes. Currently this means using --output, possibly with --replace-run. This, in turn, would mean either that ap_verify needs to know whether it's already been run in the same workspace, or that it needs to autonomously set up the same type of chained collection as expected by pipetask run.