Skip to content

Releases: moritzzimmer/terraform-aws-lambda

v7.6.1

16 Sep 07:50
Compare
Choose a tag to compare

v7.6.0

16 Sep 07:45
Compare
Choose a tag to compare

What's Changed

  • chore(github): bump actions/cache from 3 to 4 by @dependabot in #122
  • fix: use lambda resource to get name instead of variable by @elliottohara in #130
  • feat: support sns redrive policy by @saefty in #129
  • chore(github): bump aquasecurity/trivy-action from 0.16.1 to 0.18.0 by @dependabot in #124
  • fix: fixed possible race conditions for SNS subscriptions by @moritzzimmer in #131
  • chore(github): bump aquasecurity/trivy-action from 0.18.0 to 0.19.0 by @dependabot in #132
  • chore(github): bump aquasecurity/trivy-action from 0.19.0 to 0.21.0 by @dependabot in #136
  • chore: migrated to trivy and bumped tflint rules by @moritzzimmer in #137
  • feat(vpc): added dual-stack support in ipv6 enabled VPCs by @moritzzimmer in #146

Full Changelog: v7.5.0...v7.6.0

v7.5.0

19 Jan 09:20
780a686
Compare
Choose a tag to compare

What's Changed

Full Changelog: v7.4.1...v7.5.0

v7.4.1

12 Jan 11:36
0ba2716
Compare
Choose a tag to compare

What's Changed

Full Changelog: v7.4.0...v7.4.1

v7.4.0

12 Jan 10:50
300e112
Compare
Choose a tag to compare

What's Changed

Full Changelog: v7.3.0...v7.4.0

v7.3.0

17 Nov 08:33
6f0d1e3
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v7.2.0...v7.3.0

v7.2.0

12 Oct 11:48
5033ef2
Compare
Choose a tag to compare

What's Changed

  • feat: code pipeline names can be up to 100 characters by @thisismana in #102

Full Changelog: v7.1.0...v7.2.0

v7.1.0

28 Sep 11:37
02e1888
Compare
Choose a tag to compare

What's Changed

Full Changelog: v7.0.0...v7.1.0

v7.0.0

26 Sep 11:57
9be8d18
Compare
Choose a tag to compare

Breaking changes

Minimum Terraform and AWS provider versions

Minimum versions of Terraform and the AWS provider have been bumped to it's latest versions. Make sure to upgrade your environment to use Terraform >-= 1.0 and your projects to use AWS Provider >= 5.0.

Refactored S3 based CodePipelines

S3 based deployments relied on CloudTrail (via EventBridge) to propagate uploads of Lambda packages to S3 and start the corresponding CodePipeline. This has been refactored to use S3 Bucket notifications which is the recommended approach by aws.

Make sure to activate S3 bucket notifications for the source bucket of your Lambda function to keep your continuous deployment pipelines working:

resource "aws_s3_bucket" "source" {
  bucket        = "my-ci-bucket"
  force_destroy = true
}

resource "aws_s3_bucket_notification" "source" {
  bucket      = aws_s3_bucket.source.id
  eventbridge = true
}

see S3 or complete for examples and README for details.

If you created a CloudTrail solely for starting your Lambda pipelines you may delete it after migrating to bucket notifications.

Thanks to @saefty for providing this refactoring.

What's Changed

  • feat(deployment)!: use s3 native notifications over cloudtrail logging by @saefty in #96
  • chore(deployment): bumped default base image for CodeBuild by @moritzzimmer in #97
  • chore(deployment): use python 3.11 in CodeBuild by @moritzzimmer in #99
  • chore!: bumped minimum terraform and aws provider versions by @moritzzimmer in #98

Full Changelog: v6.13.0...v7.0.0

v6.13.0

16 May 11:14
Compare
Choose a tag to compare

What's Changed

  • feat: permit lambda write access only to it's own logs by @Mi3-14159 in #95

Full Changelog: v6.12.0...v6.13.0