Can't stop a deprecated API

[exalate-issue-sync]

Describe the bug :

The issue is when upgrading from APIM version from 3.5 to 4.1.3. If we have v1 APIs that are deprecated where we have a deadlock scenario. If the APIs are left deprecated and started, we cannot stop them or upgrade them to v2. And since they are not stopped, the APIs can also not be deleted. The only way to remove the APIs is to delete them from your database. I believe that not allowing APIs to be deprecated, unless they are stopped might be a possible solution to avoid issues like this.

To Reproduce :

Steps to reproduce the behaviour: 1. I am using PostgreSQL and APIM version 3.5.0 2. Create some v1 APIs 3. Start, publish and deploy them and after that deprecate them 4. Now upgrade from version 3.5.0 to version 4.1.3 (regardless of the version I believe the issue can be replicated in any 4.x version and probably in 3.20.x) 5. Now when you open your APIs you shouldn't be able to upgrade or delete the APIs: https://p28.zdusercontent.com/attachment/1227727/vxD2eH93LmGP9m87fQWn8HFwr?token=eyJhbGciOiJkaXIiLCJlbmMiOiJBMTI4Q0JDLUhTMjU2In0..Ckk4WLSB93XVKgMktZwv3w.MIicxdqh0AVxIrznRspbKaRUBv_1jIJn8GuFo7laPDBatpQKYuP1sGd5yE4jY9qoXjyaixlZ-Z87T1B54YjQhQ39iRFN-OmUcHDks6N_tRdw7vzLhaZF98kLLiMMwgN2QEDgmKs3aWi_aLy7uIhF7HB1M-4ttGkFYrFsob7Aecyn0QV50BrKoENoePSlERShPOgEgY_f1WJqX8qK9mWvfpxN76i7IuoPzLYNmu3mebNYDD7ofVfk0YrgKWu15F2SFZE-bfo1X2o5LGu8wtSu1rlqPIwprvPdAhsXBnc8VtM.2L18o-EmbcLtwpO9v_ZGAQ

Desktop :

• Environment: Gravitee APIM 4.1.3
• Browser: Google Chrome

[exalate-issue-sync]

This issue will be fixed in versions 4.0.14, 4.2.0, 4.1.5