Customize shutdown signal to send SIGINT to Postgres

[bgandon]

Hi,

After submitting cloudfoundry/bosh#2320 as a “short path PR”, we've implemented here a new sutdown_signal configuration in BPM.

This new config accepts INT or TERM (the default), so that BPM can properly trigger the Fast Shutdown Mode of Postgres. This simplifies things, and doesn't require a drain script for the standard requirement that the executable expects a SIGINT instead of a SIGTERM.

After this is merged, we' submit a refactor PR in cloudfoundry/bosh so that it is used instead of the drain scripts we have proposed in cloudfoundry/bosh#2320

Co-authored-by: Jörg Weisbarth

[bosh-admin-bot]

This pull request was marked as Stale because it has been open for 21 days without any activity. If no activity takes place in the coming 7 days it will automatically be close. To prevent this from happening remove the Stale label or comment below.

[ragaskar]

Hi:

We looked at this commit and noticed that the behavior of bpm stop <process> when the process doesn't exist was changed. It previously printed a message about missing process + exited successfully, now it prints a message about missing configuration and exits with a failure code. Was this intentional? It looked like it could be fixed with the following commit: 8ead4d3

what do you think?

Also, would you be open to/interested in supporting all signals that kill takes?

[selzoc]

Hi @bgandon ! @ragaskar and I are going to merge this and do some follow-on work before cutting a release. Thanks for the contribution!

[selzoc]

This is now in release v1.1.14 🎉