You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because you support file-name in lambad-invoke, so I can use other js file name, not default index.js. But if I use customized js file name, it doesn't work after deploy, because js file name is changed. To support it you have to support "handler" in lambda-deploy.
The text was updated successfully, but these errors were encountered:
I think you might need to change the handler settings for your function, by default it's index.handler but according to the documentation in the AWS console the first component is the file name:
The module-name.export value in your function. For example, "index.handler" would call exports.handler in index.js.
Once you set the handler manually in the function settings does it persist after you deploy? It should leave any unsupported settings unchanged when deploying.
Adding support to set the handler is probably still a good idea though.
Because you support file-name in lambad-invoke, so I can use other js file name, not default index.js. But if I use customized js file name, it doesn't work after deploy, because js file name is changed. To support it you have to support "handler" in lambda-deploy.
The text was updated successfully, but these errors were encountered: