add support for S3 object based TF state lock @smangels (#192)
## whatThis 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 @osterman (#190)
## what - Update go `1.24`why
- Error loading shared library libresolv.so.2 in Go 1.20
References
Replace Makefile with atmos.yaml @osterman (#189)
## what - Remove `Makefile` - Add `atmos.yaml`why
- Replace
build-harness
withatmos
for readme genration
References
- DEV-3229 Migrate from build-harness to atmos
Migrate new test account @osterman (#182)
## what - Update `.github/settings.yml` - Update `.github/chatops.yml` fileswhy
- Re-apply
.github/settings.yml
from org level to getterratest
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