Skip to content

terraform lockfile to s3 use_lockfile from dynamodb_table - #249

Merged
ale210 merged 1 commit into
mainfrom
218-terraform-lockfiles-use-s3-not-dynamodb
Oct 3, 2026
Merged

ale210 merged 1 commit into
mainfrom
218-terraform-lockfiles-use-s3-not-dynamodb

Conversation

@here

@here here commented Oct 1, 2026 •

Copy link
Copy Markdown
Member

Terraform 1.11+ supports native S3 lockfile locking, making the DynamoDB-based lock table deprecated. Both prod.backend.tfvars and backend.tf currently print a Deprecated Parameter warning on every plan/apply run.

Refs hackforla/devops#218

What changes did you make?

  • Delete the dynamodb_table = "hfla_incubator_terraform_table" line and add use_lockfile = true.
  • Add a no-op comment line to any .tf file in the same PR.

Why did you make the changes (we will use this info to test)?

Terraform 1.11+ supports native S3 lockfile locking, making the
DynamoDB-based lock table deprecated. Both prod.backend.tfvars and
backend.tf currently print a Deprecated Parameter warning on every
plan/apply run.
@github-actions

github-actions Bot commented Oct 1, 2026 •

Copy link
Copy Markdown
Contributor

Terraform plan in terraform
With backend config files: terraform/prod.backend.tfvars

No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

✅ Plan applied in Terraform apply (OIDC) #98

@ale210 ale210 changed the title terraform lockfile to s3 use_lockfile from dynamodb_table (#218) terraform lockfile to s3 use_lockfile from dynamodb_table Oct 3, 2026
@ale210
ale210 merged commit 86c16d5 into main Oct 3, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants