Skip to content

Latest commit

 

History

History
42 lines (24 loc) · 1.57 KB

UPGRADING.md

File metadata and controls

42 lines (24 loc) · 1.57 KB

Upgrading Notes

This document captures required refactoring on your part when upgrading to a module version that contains breaking changes.

Upgrading to v2.0.0

Variables (v2.0.0)

The following variables have been replaced:

  • permissions_boundary → execution_role.permissions_boundary
  • policy → execution_role.policy
  • role_arn → execution_role_custom.arn
  • role_prefix → execution_role.name_prefix

The following variables have been introduced:

  • execution_role.additional_policy_arns. Add additional policy arns to the execution role.
  • execution_role.path. Customizable role path.

The following variables have been removed:

  • create_policy. This variable is not deemed necessary anymore, creating the policy is controlled by providing an execution_role.policy.

The following variable defaults have been modified:

  • runtime → default: python3.13 (previous: python3.10).

Upgrading to v1.0.0

Behaviour (v1.0.0)

The need to provide a providers = { aws.lambda = aws } argument has been removed. When using v1.0.0 or higher the provider will simply default to aws and if a different provider is needed, one can be provisioned by passing down providers = { aws = aws.lambda }.

Variables (v1.0.0)

The following variable defaults have been modified:

  • log_retention → default: 365 (previous: 14). In order to comply with AWS Security Hub control CloudWatch.16.
  • runtime → default: python3.10 (previous: python3.9).
  • tags → default: {} (previous: ``). We recommend to set tags on the specified AWS provider.