Skip to content
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

Support handler in lambda-deploy #33

Closed
flyingsky opened this issue Sep 18, 2015 · 3 comments
Closed

Support handler in lambda-deploy #33

flyingsky opened this issue Sep 18, 2015 · 3 comments

Comments

@flyingsky
Copy link

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.

@Tim-B
Copy link
Owner

Tim-B commented Nov 3, 2015

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.

@flyingsky
Copy link
Author

Yes, I have to change handler settings. Unfortunately this plugin deploy function doesn't support to change handler setting.

@Tim-B
Copy link
Owner

Tim-B commented Nov 8, 2015

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants