fix: Handle SIGTERM process kill signal #6697
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue(s) does this change fix?
#6688
Why is this change necessary?
Handles the case where a local service starts up, and is terminated by a non-control-c (SIGINT) signal.
For example, users running SAM CLI inside of a Docker container will see issues where containers aren't cleaned up since Docker sends a SIGTERM signal which is currently unhandled by SAM CLI.
How does it address the issue?
Adds a SIGTERM handler that unblocks the thread and control flow is handed back to the main thread to finish execution/clean-up.
What side effects does this change have?
N/A
Mandatory Checklist
PRs will only be reviewed after checklist is complete
make pr
passesmake update-reproducible-reqs
if dependencies were changedBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.