Regression: API project DELETE backwards incompatible change
Summary
GitLab 12.6 introduced soft deletion of projects. The problem is that through API calling "project DELETE" now also just marks the project for deletion, but does not really delete it. This broke some of our scripts which assume that the project is really immediately deleted before they try to create it again. We use this in our migration script which sometimes fails so we want to clear up state before retrying.
What is the current bug behavior?
That the project was deleted before immediatelly through API, but now it is not anymore.
What is the expected correct behavior?
To have backwards compatible changes inside minor version bumps. Or at least to have a flag in the API we can turn on/off to control the behavior.
Output of checks
This bug happens on GitLab.com