2.1.0

Team Digital Usage with Datadog

For Team Digital services, use this configuration to ensure logs reach the correct Datadog tenant:

module "lambda" {
  source = "github.com/nsbno/terraform-aws-lambda?ref=x.y.z"

  department_override = "digital"
  team_name_override = "dx"

  # ... rest of your configuration goes here

```}

## What's Changed
* Add department_override variable and update Datadog API key logic to support multiple datadog instances by @tomarnebra in https://github.com/nsbno/terraform-aws-lambda/pull/16

## New Contributors
* @tomarnebra made their first contribution in https://github.com/nsbno/terraform-aws-lambda/pull/16

**Full Changelog**: https://github.com/nsbno/terraform-aws-lambda/compare/2.0.0...2.1.0

2.0.0

Important

Version 2 and over requires the usage of platform-actions, our GitHub Actions-based workflows.

How to upgrade from v1?

1. Upgrade Vy provider. Find where you have defined required_providers, and add/bump verisons:

terraform {
  required_providers {
    vy = {
      source  = "nsbno/vy"
      version = ">= 1.0.0, <2.0.0"
    }
  }
}

2. Add new vy_lambda_artifact data resource

data "vy_lambda_artifact" "this" {
  # Replace with your service GitHub repository name
  github_repository_name = "infrademo-demo-app"
}

3. Point to the new resource in the artifact parameter

module "lambda_s3" {
  source = "github.com/nsbno/terraform-aws-lambda?ref=x.y.z"

  service_name = "get-users"

  artifact_type = "s3"
  artifact      = data.vy_lambda_artifact.this

  runtime = "python3.11"
  handler = "handler.main"

  memory = 256
}

Do you have a monorepo with multiple lambdas?
See this example

What's Changed

• Bump Datadog layer versions and Lambda Insights version
• Add support for Vy provider for V2 version handling by @rotciw in #15
• Update examples for multiple use cases

Full Changelog: 1.1.0...2.0.0

1.2.0

• Bump Lambda Layer versions
• Refactor Datadog configuration to use options object for environment variables

To configure, use:

datadog_options = {
  profiling_enabled       = false
  trace_enabled           = true
  logs_injection          = true
  merge_xray_traces       = false
  serverless_logs_enabled = true
  capture_lambda_payload  = false
}

Full Changelog: 1.1.0...1.2.0
Full Changelog: 1.1.0...1.2.0

2.0.0-rc2

• Allow specifying service account id to automatically fetch artifact information

Full Changelog: 2.0.0-rc1...2.0.0-rc2

2.0.0-rc1

What's Changed

• Update implementation to support new GHA based pipeline by @rotciw in #14

Full Changelog: 1.1.0...2.0.0-rc1

1.1.0

[Intended for Digital]

• Add option to override datadog team name
• Add option to override datadog api key secret

Full Changelog: 1.0.2...1.1.0

1.0.2

• Set DataDog profiling to default false, as it reverts lambda extension to a compability version
• Bump Lambda layer versions

Full Changelog: 1.0.1...1.0.2

1.0.1

What's Changed

• Fix custom log group name by @thaugrud in #13

New Contributors

• @thaugrud made their first contribution in #13

Full Changelog: 1.0.0...1.0.1

1.0.0

Note

Major Version Release

Read this Confluence Page for Datadog setup instructions

What's Changed

• Changed name -> service_name
• Added component_name to create a distinction when multiple lambdas belong to one service
• Add support for python 3.13
• Add Datadog by @rotciw in #2

Full Changelog: 0.7.0...1.0.0

1.0.0-rc4

Note

Read this Confluence Page for setup instructions

What's Changed

• Update layer versions

Full Changelog: 1.0.0-rc3...1.0.0-rc4