[Feature] Graceful shutdown on KeyboardInterrupt event about dbt-core HOT 2 CLOSED

Thanks for opening this @gorandumic !

I think we'd like to keep things as simple as possible and keep the current behavior where dbt only closes the connections and aborts the run without attempting any other database actions.

So rather than making one last attempt of writing state to the database, we'd like dbt to terminate as expediently as possible. I realize that you're specifically targeting custom logging to the database, but as a fall-back there may be some logging in the logs or target directories that can be utilized instead.

from dbt-core.

@dbeatty10 I understand you wouldn't want to change anything but many people are requesting this feature. Because abruptly halted execution does not follow any software development standards, seems more like an unhandled exception scenario to me. You wouldn't even consider a conditional cli flag to support this feature? This way it would not be a breaking change and we could choose whether we ignore the interrupt or not.

from dbt-core.