Skip to content

CHANGELOG.md

Latest commit

 

History

History
85 lines (70 loc) · 3.63 KB

CHANGELOG.md

File metadata and controls

85 lines (70 loc) · 3.63 KB

Unreleased

BACKWARDS INCOMPATIBILITIES / NOTES:

  • This module is now compatible with Terraform 1.3 and higher.
  • This module is now compatible with the Terraform AWS provider 4.22 and higher.
  • The lambda_assume_role var is now called lambda_assume_role_policy_document.
  • The lambda_execution_policy var is now called lambda_execution_role_policy_document.
  • The account_id var has been removed and the current account is instead determined from a data resource.
  • The publish var now accepts a boolean value rather than a "yes"/"no".
  • The deploy_in_vpc var now accepts a boolean value rather than a "yes"/"no", has been renamed to include_vpc_access and defaults to false.

IMPROVEMENTS

  • Added support for using a container instead of a zip file to specify the lambda function, via the lambda_package_type variable, which defaults to "Zip", the lambda_image_uri variable and the lambda_image_config variable.

    When lambda_package_type is "Image", lambda_image_uri must be specified and lambda_zip_path, lambda_handler and lambda_runtime should not be specified.

  • The execution role created for use by the lambda function no longer includes a statement for VPC access management unless include_vpc_access is true.

  • The execution role statements for VPC access management and log management can now be disabled using the variables include_execution_role_policy_vpc_access_management_statement and include_execution_role_policy_log_management_statement.

  • The target lambda architectures can now be provided to the lambda using the lambda_architectures variable.

  • Tracing configuration for the lambda can now be specified using the lambda_tracing_config variable, and a corresponding tracing execution role statement is added to the role when this variable is present.

  • Logging configuration for the lambda can now be specified using the lambda_logging_config variable.

  • A log group is now created for the lambda unless the include_lambda_log_group variable is false. This log group is configured as the log destination for the lambda unless the lambda_logging_config variable includes a log_group parameter, referring to a log group name, in which case the provided log group is used.

1.0.0 (May 28th, 2021)

BACKWARDS INCOMPATIBILITIES / NOTES:

  • This module is now compatible with Terraform 0.14 and higher.

0.1.5 (November 27 2020)

IMPROVEMENTS:

  • Added a new deploy_in_vpc flag to disable VPC deployments.

    This enables the lambda to be used more easily when you want to access global AWS Services without having to configure a VPC or routing. To avoid breaking changes, the default mode is to deploy inside a VPC environment.

    When deploy_in_vpc is set to "no", the sg_lambda security_group is not created and the vpc_config is passed empty values to create an AWS Lambda outside a VPC.

  • Added tags input to tag terraform managed resources

    A map of AWS tags can now be passed in via the tags input variable. The default tags are:

    {
  "Component": "<component>",
  "DeploymentIdentifier": "<deployment_identifier>"
}

  • Removed the hard-coded AWS region and AWS account ID's in lambda_execution_policy.

  • Added include_route53_zone_association = "no" to test prerequisites to simplify test harness deployment

  • Added "ec2:AssignPrivateIpAddresses", "ec2:UnassignPrivateIpAddresses" to default execution policy to bring it inline with Amazon's default AWSLambdaVPCAccessExecutionRole.

  • Added an optional lambda_description variable.

  • Added descriptions to variables for improved IDE code hints.