KuduSync does not delete files that were created by a failed deployment #37
Description
We have encountered this a few times.
- file migrations/0026_auto_20190408_1538.py is added to source control and pushed to Bitbucket
- triggers deployment
- deployment fails
- we delete migrations/0026_auto_20190408_1538.py and push
- triggers deployment
- deployment still fails because the erroneous file still exists
I believe this is happening because on a failed deployment, the manifest is not saved, so when KuduSync looks for the previous manifest to determine what to delete, it doesn't see the file it should be deleting.