这是indexloc提供的服务,不要输入任何密码
Skip to content

Conversation

@pawelpesz
Copy link

With the advent of Terraform 1.11, DynamoDB table locking has been deprecated, and native S3 locking via the use_lockfile argument has become the recommended locking option.

While you can still use DynamoDB alongside S3-native state locking for migration purposes, we encourage migrating to the new state locking mechanism.

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

The PR adds a self-explanatory create_dynamodb_table variable (set to false by default, to maintain backward compatibility) along with a terraform_iam_policy_add_lockfile_permissions variable that controls whether the extra S3 permission required for S3 state locking is added to the Terraform policy. It also includes a policy refactor and tflint configuration refresh.

The PR fixes the following issue:

#128

@pawelpesz
Copy link
Author

Hello @nozaq, thank you for the excellent module. I would very much appreciate it, if you could take a look at this PR, it adds a couple of features necessary for Terraform 1.11+ 🙌

@pawelpesz
Copy link
Author

Hi @nozaq, any chance of a review? I'd hate to have to use a forked version of the repo.

@pawelpesz pawelpesz force-pushed the feat/dynamodb-table-optional branch from f95fd9a to f52b1df Compare May 13, 2025 15:04
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.

1 participant