cancelling chef-server-ctl cleanse --with-external still acts on external sources

[acranox]

Running chef-server-ctl cleanse --with-external and then typing CTRL-C will proceed to attempt cleanse the external solr and postgresql data.
It should actually abort.
This is with 12.14.0. I have not tested other versions.

# chef-server-ctl cleanse --with-external
    *******************************************************************
    * * * * * * * * * * *       STOP AND READ       * * * * * * * * * *
    *******************************************************************
    This command will delete *all* local configuration, log, and
    variable data associated with Chef Server.
    This will also delete externally hosted Chef Server data.
    This means that any service you have configured as 'external'
    will have any Chef Server permanently deleted.

    You have 60 seconds to hit CTRL-C before configuration,
    logs, local, and remote data for this application are permanently
    deleted.
    *******************************************************************

^C
Deleting data from external service: opscode-solr4
Cleansing data in a remote Sol4 instance is not currently supported.
Deleting data from external service: postgresql
Chef Server databases and roles have been successsfully deleted from your_database.rds.amazonaws.com

[marcparadise]

Ouch, I'm sorry that you ran into that - thanks for reporting it.

We'll do some digging, as I'd like to know if any of our recent platform upgrades (ruby and various gems) are related, or it was in there from the start.

That aside, here's the omnibus-ctl PR that resolves it: chef/omnibus-ctl#56

I will close this issue once we pull that change into a build for current of chef-server.

[PrajaktaPurohit]

@acranox I am really sorry it has taken us so long to get back to you. The change @marcparadise mentioned is still outstanding but we have made to prioritize this issue.