Removed production items reporting "Errored" deployments #907
Description
I have noticed a number of "Ended in Error" entries in my interop Deployment history logs:
They all show the same "Class [name] does not exist for config item [name]" error even though they are for different config items. When I look at the first deployment that errored, it was for the specified class and config item. I think what happened is that I switched away from a feature branch where this class and item were introduced. (For some reason, this error carried through to a number of other deployments, but I believe that is separate issue/red herring)
Changing feature branches makes it look like these items were deleted from git, so the Incremental Load pull handler deletes them from the instance. The problem is that it deletes everything one by one in lexicographic order, which means the classes get deleted before the production items because all my classes are in the ./cls directory and all my production items are in ./ptd.
When I manually delete items in this sequence (Class, then production item), I get a similar JavaScript alert that the class does not exist. (the item then disappears from the production, but the corresponding file is not deleted from git... A similar bug that probably warrants its own issue.)
The Incremental Load pull handler needs to consider file type when deleting files and should delete production items before any other kind of item. (similar to how it loads classes before production items)
$zv: IRIS for Windows (x86-64) 2025.1 (Build 223U) Tue Mar 11 2025 18:14:42 EDT
Embedded Git: v2.14.0