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
Currently, you have to specify the handler for a function like so;
functions:
MyLambda:
handler: Lambdas/MyLambda/index.handler
With this approach, when the serverless deploy command is executed, it pushes up the entire folder for Lambda's into every Lambda function, so you will get other lambda function code in a path in a lambda, which is silly.
Description
What is the use case that should be solved. The more detail you describe this in the easier it is to understand for us.
This should be solved by specifying a "path" property so we can chose, for MyLambda, the code is here, and thus this should be deployed to this lambda function only.
This is a Feature Proposal
Currently, you have to specify the handler for a function like so;
functions:
MyLambda:
handler: Lambdas/MyLambda/index.handler
With this approach, when the serverless deploy command is executed, it pushes up the entire folder for Lambda's into every Lambda function, so you will get other lambda function code in a path in a lambda, which is silly.
Description
This should be solved by specifying a "path" property so we can chose, for MyLambda, the code is here, and thus this should be deployed to this lambda function only.
e.g.
functions:
BetPlacementLambda:
path: Lambdas/MyLambda
handler: index.handler
Similar or dependent issues:
The text was updated successfully, but these errors were encountered: