Lambda Bundles

PR	Champion
#	@eladb

Description

• NodeFunction, JavaFunction, PythonFunction, etc.
• Automatic publishing of environment variables
• Combine “grant” & publish (e.g. bucket.grantXxx(lambda) will also add BUCKET_ARN environment variable)

Progress

• Tracking Issue Created
• RFC PR Created
• Core Team Member Assigned
• Initial Approval / Final Comment Period
• Ready For Implementation
  • implementation issue 1
• Resolved

[jogold]

Hey @eladb, I’m sure you’ve seen https://github.com/aws/aws-cdk/pull/6535… I’ve been working further on this to come up with the best possible developer experience for JS/TS Lambda functions.

I have now a working construct offering the following API:

Code can be defined inside the construct and it can use any top level dependency imported in the file (another file or an external module). This offers a really great developer experience. I’m using the Typescript Compiler API to analyze the AST for this.

It ~can also easily support~ supports props like externals (= a list of module that should not be bundled like aws-sdk) and natives (= a list of modules that should be included/installed in the node_modules folder, can be done in a Lambda compatible docker image). The whole process could be dockerized.

We can discuss this further when you’re available.

[eladb]

I tend to agree that synth is more inline with how we want CDK experience to work. Ideally we should offer some kind of an open framework for building assets inside docker images during synthesis.

The minimal surface can be something like "run this command inside a docker image with two mounted volumes: /src with the project source tree and /asset is mounted to where the asset output should be emitted (could be a directory or a file).

Then, we can implement our parcel bundler using something like this, and also perhaps implement an additional builder that leverages sam build.