Disable signal handlers on AWS lambdas via env var #462
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This allows babashka to be run in an AWS lambda.
borkdude
changed the title
|
Thanks! Two minor remarks:
Related PR: #305 |
…L_HANDLERS Any signal handler used in AWS lambdas will not work. This simplifies/shortens the naming of the env var.
Sounds good. Made the suggested changes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The introduction of shutdown hooks from v0.0.81 prevents babashka from running in an AWS lambda. This PR allows disabling the hook through the same env var for disabling the pipe signal handler and renames the env variable for simplicity.