Idea: API Lifecycle support

[DonMartin76]

See also #25:

Deleting an abandonded API is perfectly fine and should be possible. Right now it's not that simple to do that right, as deleting an API requires all subscriptions to be deleted first. To make this simpler, the following functionality would be good:

• Add a possibility to "deprecate" an API, so that it's no longer possible to subscribe to it, but existing subscriptions are still in effect, as would documentation and Swagger still be available
• Add a "download subscriptions CSV" functionality which would let an Admin download a list of existing subscriptions for e-mailing actions announcing the retirement of an API
• Have an Admin functionality which lets an Admin delete all active subscriptions of an API
• In the kickstarter, add a "do you really know what you're doing" kind of alert in the kickstarter when deleting APIs.

Thoughts? Is this aiming too low, are there other big problems that need to be taken care of?

[TESAARON]

Hi Martin,

I think the admin control would be an important feature. Just gives super user access in case developer mistakes like this are made. Also the extra dialogue window to prompt the user would be good.

Aaron

[DonMartin76]

The problem you had with somebody acccidentally deleting an API will get a safety question; but as the kickstarter cannot know the state of the actual deployment, you will still need to keep in mind that you may still have existing subscriptions.

Sneak peeks (I decided this is important enough to have it in 0.10.0):

This view is only displayed on the API page if you're logged in as an Admin; otherwise you won't see this.

This is displayed if the API has a "deprecated" property in the apis.json set to true. The kickstarter will get support for this as well.

[DonMartin76]

Done.