v0.26.1

🚀 Enhancements

Add var.ttl_enabled to support disabling ttl @mwarkentin (#85)

what

• Add var.ttl_enabled to support explicitly disabling dynamodb ttl on a table

why

• Unable to disable an existing ttl configuration

references

• Closes #84

Example Plan

After setting ttl_enabled = false w/ blank ttl_attribute:

# module.ddb_transaction_event.aws_dynamodb_table.default[0] will be updated in-place
  ~ resource "aws_dynamodb_table" "default" {
        arn              = "arn:aws:dynamodb:us-east-1:***********:table/devmw-transactionEvent"
        billing_mode     = "PAY_PER_REQUEST"
        hash_key         = "transactionId"
        id               = "devmw-transactionEvent"
        
...

        timeouts {}

      ~ ttl {
            attribute_name = "Expires"
          ~ enabled        = true -> false
        }
    }

v0.26.0

Dynamodb table replica support @mwarkentin (#83)

what

• This feature will allow setting replica configurations for aws_dynamodb_table resource.

why

• According to the note at AWS provider v3.4.0 docs, it's recommended to use replica configuration instead of aws_dynamodb_global_table resource and there is a lack of that functionality in this module.

references

• Closes #41
• Replaces #66, #82

v0.25.2

🤖 Automatic Updates

context.tf updated to v0.24.1, minimum required Terraform version bumped to 0.13.0 when needed, readme updated @maximmi (#80)

what

• update context.tf to v0.24.1
• minimum required Terraform version bumped to 0.13.0
• readme updated, Bridgecrew compliance badges added

why

• It allows for setting the letter case of tag names and labels, back compatibility with context v0.22.0 and below
• we have dropped support for Terraform 0.12
• To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliant

v0.25.1

🤖 Automatic Updates

Update context.tf @cloudpossebot (#81)

what

This is an auto-generated PR that updates the context.tf file to the latest version from cloudposse/terraform-null-label

why

To support all the features of the context interface.

v0.25.0

minimum required Terraform version bumped to 0.13.0, context.tf updated, readme updated @maximmi (#78)

what

• update context.tf to v0.23.0
• minimum required Terraform version bumped to 0.13.0
• readme updated, Bridgecrew compliance badges added

why

• It allows for setting the letter case of tag names and labels
• we have dropped support for Terraform 0.12
• To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliant

v0.24.0

Terraform 0.14 upgrade @maximmi (#76)

what

• Upgrade to support Terraform 0.14 and bring up to current Cloud Posse standard

why

• Support Terraform 0.14

v0.23.0

terraform 0.14 upgrade including context.tf @Nuru (#72)

what

• Upgrade to support Terraform 0.14 and bring up to current Cloud Posse standard, including context.tf

why

• Support Terraform 0.14
• Closes #64, closes #71

v0.22.0

Add possibility to define custo kms key for server side encryption @dmitriy-lukyanchikov (#68)

what

• Add possibility to define custom kms key for server-side encryption

why

• its useful when you want to create you on custom managed KMS key

v0.21.0

allow to add additional attributes and tags to autoscaler @etwillbefine (#52)

what

This is to avoid adding a region prefix to dynamodb tables because the autoscaler IAM role requires additional region indicator in its names

why

• IAM policies and roles need to be unique
• DynamoDB tables should not have a region indicator as they are regional

v0.20.0

update terraform-aws-dynamodb-autoscaler version @woz5999 (#65)

what

set minimum versions for providers without pinning to a specific major version

why

the current method makes it very difficult to maintain or upgrade consistent provider versions within a project

references

https://www.terraform.io/docs/configuration/provider-requirements.html#best-practices-for-provider-versions