-
Notifications
You must be signed in to change notification settings - Fork 250
Update function code, with function built inside a container #1740
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
Labels
bug
We can reproduce the issue and confirmed it is a bug.
Comments
You are not missing anything, we added it to Deploy Serverless but not Update Function Code. This was a miss on our part. |
@brunocuervo our next EAP release (which should come out tomorrow) fixes this and it will part of the next release |
That was fast. Thanks for the great work with the toolkit!
…On Mon, May 4, 2020, 8:40 PM Hunter Werlla ***@***.***> wrote:
@brunocuervo <https://github.com/brunocuervo> our next EAP release (which
should come out tomorrow) fixes this and it will part of the next release
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1740 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAPZ54MSSLMY55MXMUBIB2TRP5HALANCNFSM4MXO3CEQ>
.
|
This was released |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Your Environment
Question
I'm building a lambda in node that uses a native module (canvas). When running the lambda locally, I can just check the "Build function inside a container", and things are built as expected against the correct image, and not my local env. But then when I right-click the lambda and select "Update Function Code" to deploy it, it is built without the
--use-container
(I can see it in thesam build
command), and then execution fails when I run it remotely.Is there any way to deploy the lambda built in a container with the toolkit? Am I missing something?
The text was updated successfully, but these errors were encountered: