Deletion fails in case of subscriptions

[erik-am]

When running sls remove, the removal of the WSO2 API fails if an application is subscribed to it.

Example log output:

{
  response: {
    code: 409,
    message: 'Conflict',
    description: 'Cannot remove the API 7c39e8a5-4481-4b68-b9d5-4b6adaa89797 as active subscriptions exist',
    moreInfo: '',
    error: []
  },
  responseCode: 409,
  responseHeaders: {
    'content-type': 'application/json',
    date: 'Tue, 05 Oct 2021 14:56:18 GMT',
    server: "[XXXXXXX]",
    'strict-transport-security': 'max-age=15768000',
    'x-content-type-options': 'nosniff',
    'x-frame-options': 'DENY',
    'x-xss-protection': '1; mode=block',
    'content-length': '163',
    connection: 'Close'
  }
}
Serverless: [serverless-wso2-apim] Deleting [stack name].. NOT OK, proceeding further.

The desired behaviour would be that the subscription is cleaned up as well and the WSO2 is deleted.

[ramgrandhi]

Thanks for reporting this, @erik-am

I can think of a solution as to retire the api explicitly before removing it.

one approach to implement it could be to use an explicit flag like ‘sls remove —force’ to deal with the above logic. What do you think?