Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transition to S3-native state locking and deprecate DynamoDB arguments #36257

Open
wants to merge 12 commits into
base: main
Choose a base branch
from

Conversation

bschaatsbergen
Copy link
Member

  • Removed experimental verbiage from use_lockfile, as S3-native state locking is now stable and no longer considered experimental.
  • Deprecated DynamoDB-related arguments, encouraging the use of S3-native state locking instead.
  • Improved documentation to better explain S3-native state locking and highlight the deprecation of DynamoDB-related state locking.

Copy link
Member

@jar-b jar-b left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, just a typo and a couple small suggestions

website/docs/language/upgrade-guides/index.mdx Outdated Show resolved Hide resolved
website/docs/language/backend/s3.mdx Outdated Show resolved Hide resolved
website/docs/language/backend/s3.mdx Outdated Show resolved Hide resolved
website/docs/language/backend/s3.mdx Show resolved Hide resolved
@bschaatsbergen bschaatsbergen marked this pull request as ready for review January 7, 2025 14:41
@bschaatsbergen bschaatsbergen requested review from a team as code owners January 7, 2025 14:41
```console
% go test -count=1 -run="TestBackendConfig_PrepareConfigValidation" ./...
ok      github.com/hashicorp/terraform/internal/backend/remote-state/s3 0.507s
```
@bschaatsbergen
Copy link
Member Author

bschaatsbergen commented Jan 7, 2025

One thing I noticed while working on deprecating DynamoDB-related arguments is that no warning diagnostics are being surfaced to the console when you're using a deprecated argument in the s3 block. It’s something to look into, but it’s not blocking since this behavior is also present in 1.10. cc @jar-b / @gdavidson.

jar-b
jar-b previously approved these changes Jan 7, 2025
Copy link
Member

@jar-b jar-b left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🎉

% TF_ACC=1 go test ./...
ok      github.com/hashicorp/terraform/internal/backend/remote-state/s3 203.342s

@jar-b
Copy link
Member

jar-b commented Jan 7, 2025

Thanks for the updates @bschaatsbergen! 👍

Clarify S3 permissions when using S3-native state locking.
jar-b
jar-b previously approved these changes Jan 7, 2025
Copy link
Member

@jar-b jar-b left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🚀

gdavison
gdavison previously approved these changes Jan 7, 2025
Copy link
Contributor

@gdavison gdavison left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! 🚀

Co-authored-by: Ruben Nic <RubenSandwich@users.noreply.github.com>
@bschaatsbergen bschaatsbergen dismissed stale reviews from gdavison and jar-b via 9609070 January 7, 2025 18:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants