-
Notifications
You must be signed in to change notification settings - Fork 44
Add support for optional name input #11
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Thanks @jonathanmv ... yeah we are now auto generating names and the readme is out of date in that regard. But we'd love to have optional name input. |
Hi @eahefnawy. It looks like PR #16 addresses this issue. Is this something you intend to merge? |
@jhappoldt yep will test and review today. |
@eahefnawy did you have a chance to review #16 there is one more for IAM - serverless-components/aws-iam-role#4 |
@jhappoldt @eahefnawy any update on this being merged? #16 seem to be good. |
I am also interested in #16 getting merged. Is there an update? |
@eahefnawy did you find any time to review/merge this one? would be an amazing addition! |
I am also interested in #16 to get merged. Are any updates/improvements planned? |
We've released a completely new version of serverless components and updated the lambda component, which includes this change. Please check out the README for more info, as config has changed significantly: https://github.com/serverless-components/aws-lambda/ |
The
name
property gets a random id while thedescription
and other fields get the right value.Is there a different way I should set the lambda function name?
The text was updated successfully, but these errors were encountered: