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
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)
Issue details
Consider simplifying deploying lambda function code with dependencies as this is non-trivial for beginners.
An existing solution in this space is the lambda-builders library. It has CLI with a JSON-RPC interface. Scope of this library: “given a folder containing function's source code, the selected build action, and path to an artifacts folder, this library will produce built artifacts in the artifacts folder.”
Possibly Pulumi could integrate with it directly to provide a component library where you could write:
One interesting user story: https://levelup.gitconnected.com/my-journey-with-pulumi-and-the-serverless-framework-2b1398ee581a - there might be additional complications for CallbackFunction coming from closure serialization, but even if those were not fully addressed if we could guide users to a reasonable way to refactor CallbackFunctions into normal functions that could be helpful here.
Hello!
Issue details
Consider simplifying deploying lambda function code with dependencies as this is non-trivial for beginners.
An existing solution in this space is the lambda-builders library. It has CLI with a JSON-RPC interface. Scope of this library: “given a folder containing function's source code, the selected build action, and path to an artifacts folder, this library will produce built artifacts in the artifacts folder.”
Possibly Pulumi could integrate with it directly to provide a component library where you could write:
Affected area/feature
The text was updated successfully, but these errors were encountered: