-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Add hot reloading for new lambda provider #7321
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@dfangl I think We also sometimes use the prefix |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minor nits, otherwise LGTM 👍
localstack/services/awslambda/invocation/docker_runtime_executor.py
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! i can see my comments from yesterday are already addressed :-)
Motivation
For efficient lambda development, we have to provide an easy solution to hot reload lambda functions, especially those of interpreted languages (like python and nodejs).
However, we want to make it available for all managed runtimes.
It should also only reset the environments if a change is detected, to prevent unnecessary initializations.
Breaking Changes with Fallbacks
__local__
tohot-reload
. The current provider will continue to support the__local__
marker for now, the new one will only support the new one. Would move the deprecation to 1.4 and the removal to 2.0.Other Changes
Fixes #7200