Releases: telia-oss/terraform-aws-lambda
v4.2.0
v4.1.2
What's Changed
- Updates from module template: bb566f4 by @itsdalmo in #35
- Bump github.com/aws/aws-sdk-go from 1.21.7 to 1.34.0 by @dependabot in #32
- Bump golang.org/x/crypto from 0.0.0-20190701094942-4def268fd1a4 to 0.1.0 by @dependabot in #34
New Contributors
- @dependabot made their first contribution in #32
Full Changelog: v4.1.1...v4.1.2
v4.1.1
v4.1.0
v4.0.0
v3.1.0
This release adds support for specifying lambda layers, it therefore introduces a new attribute.
layers
- (Optional) List of Lambda Layer Version ARNs (maximum of 5) to attach to your Lambda Function. See Lambda Layers in Terraform Documentation
v3.0.0
This is a major rewrite of the function that contains a lot of breaking changes:
- We are using
null
values to avoid having multiple conditional versions of the lambda resource. This means that if you were deploying in a VPC, or using an S3 bucket, or both, terraform will want to destroy your old Lambda function and recreate it. You can avoid this by manually moving the state - see terraform state mv documentation. - The IAM role created should now get the same tags as the other resources.
source_code_hash
ands3_object_version
are now passed verbatim to the Lambda.
Please see the updated examples/
for current usage. We have also added a basic test suite that can be run with task e2e
(requires valid AWS credentials).
v2.0.0
v1.0.0
Final release before upgrading to terraform 0.12.
v0.4.0
-
Add support for the publish variable which is used to version lambda functions. When versioning is set to true the qualifying_arn output shows which version number the lambda function is returned. (@jentz)
-
Add support for the source_code_hash variable Used to trigger updates. Must be set to a base64-encoded SHA256 hash of the package file specified with either filename or s3_key. (@monckdav)