v1.9.0

docs: add S3 native locking documentation and fix variable descriptions Sagar Gupta (@Sagargupta16) (#197)

## what

• Fix incorrect s3_state_lock_enabled variable description (was "Whether to create the S3 bucket", now correctly describes S3 native state locking)
• Add deprecation note to dynamodb_enabled variable description linking to official Terraform docs
• Add "S3 Native State Locking" section to README with usage example

why

• Terraform 1.10+ introduced S3 native state locking via use_lockfile = true, deprecating DynamoDB-based locking
• The module already supports S3 native locking (s3_state_lock_enabled variable exists) but the documentation doesn't mention it and the variable description is incorrect
• Users are confused about how to use the module without DynamoDB (#188, #194)
• DynamoDB-based locking is officially deprecated

references

• closes #188
• closes #194
• Terraform S3 backend docs: https://developer.hashicorp.com/terraform/language/backend/s3#s3-state-locking
• DynamoDB deprecation notice: https://developer.hashicorp.com/terraform/language/backend/s3#enabling-dynamodb-state-locking-deprecated

v1.8.0

fix: update AWS provider to v6+ and correct region reference in templatefile Christian Heggland (@chrheg) (#191)

## what

• Updated the Terraform configuration to support AWS provider version >= 6.0.0
• Fixed incorrect attribute reference in the templatefile function for region resolution

why

• Ensures compatibility with newer versions of the AWS provider (v6.0.0+) to leverage updated features and improvements
• Addresses a breaking change introduced in terraform-provider-aws v6.0.0, where data.aws_region.current.name is showing depreciation warning
• Corrects the template input to use data.aws_region.current.region, aligning with the expected attribute

references

• AWS provider v6.0.0 release notes: https://github.com/hashicorp/terraform-provider-aws/releases/tag/v6.0.0
• AWS provider v6.0.0 documentation: https://registry.terraform.io/providers/hashicorp/aws/6.0.0/docs/data-sources/region
• Related breaking change PR in AWS provider: hashicorp/terraform-provider-aws#42131

v1.7.1

🚀 Enhancements

Add depends_on to S3 bucket locking resource Igor Rodionov (@goruha) (#195)

## what * Add depends_on to S3 bucket locking resource

why

• Locking can be enabled only after versioning is enabled
• Fix cold start

v1.7.0

Backend config file is not compliant with the canonical format when the S3 lockfile option is enabled Leonid Bogdanov (@vonZeppelin) (#193)

## what Generated backend config file is not compliant with the canonical Terraform format and style when the S3 lockfile option is enabled due to excessive indent. Additionally, the `use_lockfile` param is boolean, not string. ``` ...

use_lockfile = "true"

## why
After formatting the generated file with `terraform fmt` command to follow the TF style, running `terraform apply` will revert the change.
</details>

v1.6.0

add support for S3 object based TF state lock Sebastian (@smangels) (#192)

## what

This PR provides the code changes necessary to support Terraform state lock based on S3 object locks. It is closes #184 . I've decided to create the branch from release v1.5.0. Note that the change allow for smooth migration by keeping the DynamoDB related resources in place until all dependent deployments using the same framework have been migrated. After that the DynamoDB related switch can be changed to FALSE.

why

The Hashicorp Terraform project has marked the DynamoDB-based state lock as 'deprecated' and encourages the new TF state lock mechanism.

references

https://github.com/hashicorp/terraform/blob/v1.11/CHANGELOG.md#1110-february-27-2025

🤖 Automatic Updates

Fix go version in tests Erik Osterman (Cloud Posse) (@osterman) (#190)

## what - Update go `1.24`

why

• Error loading shared library libresolv.so.2 in Go 1.20

References

• https://sweetops.slack.com/archives/G014YEKDH4K/p1746672149263629
• golang/go#59305 (comment)
• cloudposse/terraform-aws-cloudfront-s3-cdn#294

Replace Makefile with atmos.yaml Erik Osterman (Cloud Posse) (@osterman) (#189)

## what - Remove `Makefile` - Add `atmos.yaml`

why

• Replace build-harness with atmos for readme genration

References

• DEV-3229 Migrate from build-harness to atmos

Migrate new test account Erik Osterman (Cloud Posse) (@osterman) (#182)

## what - Update `.github/settings.yml` - Update `.github/chatops.yml` files

why

• Re-apply .github/settings.yml from org level to get terratest environment
• Migrate to new test account

References

• DEV-388 Automate clean up of test account in new organization
• DEV-387 Update terratest to work on a shared workflow instead of a dispatch action
• DEV-386 Update terratest to use new testing account with GitHub OIDC

v1.5.0

• No changes

v1.4.2

feature: Add ability to use KMS encryption Lennart Goedhart (@pazaan) (#178)

what

• Add the ability to use KMS encryption through the addition of the sse_encryption and kms_master_key_id variables.

why

• Some business have security policies that require the use of customer-managed keys.
• As per the statement in #105, the default behavior has been left the same as it currently is.

references

• closes #105

v1.4.1

feature: Add support for deletion_protection_enabled attribute for DynamoDB Hamza aziz (@Hamza-Aziz) (#156)

what

This PR add support for the attribute deletion_protection_enabled in the DynamoDB ressource

why

To address an issue #143
To present or force DynamoDB table deletion

references

To address an issue #143
https://aws.amazon.com/about-aws/whats-new/2023/03/amazon-dynamodb-table-deletion-protection/

chore: points to correct issue in README link Matt Gowie (@Gowiem) (#154)

what

• Fixes link in README that was pointing to wrong issue

why

• We don't want to lead people astray 👍

references

• This is a redo of #153 by Tripp Lilley (@tripplilley). Fame, fortune, and internet points go to him 😄

🤖 Automatic Updates

Update README.md and docs Cloud Posse Bot (CI/CD) (@cloudpossebot) (#155)

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

Update README.md and docs Cloud Posse Bot (CI/CD) (@cloudpossebot) (#152)

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

v1.4.0

fix: s3 backend deprecated role_arn field Bas van Dijk (@basvandijk) (#151)

what

The following step was returning an error:

terraform init -force-copy

Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.
Initializing modules...
Terraform encountered problems during initialisation, including problems
with the configuration, described below.

The Terraform configuration must be valid before initialization so that
Terraform can determine which modules and providers need to be installed.
╷
│ Error: Argument or block definition required
│
│   on backend.tf line 9, in terraform:
│    9:     assume_role.role_arn = ""
│
│ An argument or block definition is required here. To set an argument, use the equals sign "=" to introduce the argument value.
╵

🤖 Automatic Updates

Update README.md and docs Cloud Posse Bot (CI/CD) (@cloudpossebot) (#150)

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

v1.3.0

fix: Better TF formating when dynamodb_table is empty when creating backend template file Salvador Montiel (@SMontiel) (#149)

what

Improve TF formatting when a DynamoDB table is not specified.

why

As our CI pipeline checks formatting and we don't use a DynamoDB for locking, we keep committing changes made to the backend file which is handled by this module.

references

N/A