Replies: 3 comments 1 reply
-
I always just use Anton's module. It can build the lambda package as part of the regular terraform plan, and accounts for diffs/updates on the source to build a new package. https://github.com/terraform-aws-modules/terraform-aws-lambda |
Beta Was this translation helpful? Give feedback.
-
@npalm Wouldn't there also be cost accrued by your company to host an S3 bucket for everyone else to consume as well? Or would it be a negligibly low cost due to size of release with older releases getting archived? I can first hand attest to messing up the setup of the zip files (#1762). |
Beta Was this translation helpful? Give feedback.
-
A less prettier solution might be to check-in the dist folder from So similar to:
^ These would somehow get generated and checked in as part of the PR process. This is of course very much less than ideal however I am simply thinking out loud about alternatives. |
Beta Was this translation helpful? Give feedback.
-
Currently we publish the lambda's as part of the release, added as assets to the GitHub release. Using the assets is a bit of cumbersome in my view. We have provided some Terraform code to download the Lambda's. But it is easy to make a mistake and have the wrong version downloaded. Also the artifacts are not validated. Alternatively lambda's can be build your self, however you have guarantee that you have the correct sources it remains custwom work.
A thought is pubish the lambda's as zip files (signed) in a public S3 bucket. Seems easy, but ouw company applies some strict rules about S3 buckets. So I am just wondering if someone has some other suggests, or do you also thin published signed artifacts in S3 is the most logicial choice. The one best fitting in the AWS eco system.
Beta Was this translation helpful? Give feedback.
All reactions