Move lambda packager to a CodeBuild docker container

[ktruckenmiller]

The node packager doesn't have make packages like the python packager does. What I'm proposing we do is build the lambda packager from the codebuild 4.0 image and, via the settings, determine which runtimes to use. Then we can have a single lambda Dockerfile to maintain and all the codebuild languages ​​available. Go, ruby, node, python, java lambdas all in one. Easier to add our basic things too like make in this single package.

During this change we should consider generating the sha of the package as well. A sha would help us manage deploys to lambda, lambda versions, and lambda @ edge and only update when code actually changes. Generate a sha of the package so we can know if the code is changed or not and pass this info to Drone / cloudformation.

• use the codebuild 4.0 image
• move the entrypoint to env var that targets the language entrypoint
• remove folders for all different languages

[Syntactical01]

Isn't codebuild ungodly slow? Or can we use their docker image outside of the actual code build service?

[Syntactical01]

Is this what you are proposing: https://hub.docker.com/r/amazon/aws-codebuild-local