-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
base: main
Are you sure you want to change the base?
Transition to S3-native state locking and deprecate DynamoDB arguments #36257
Conversation
There was a problem hiding this 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
Co-authored-by: Jared Baker <jar-b@users.noreply.github.com>
Co-authored-by: Jared Baker <jar-b@users.noreply.github.com>
```console % go test -count=1 -run="TestBackendConfig_PrepareConfigValidation" ./... ok github.com/hashicorp/terraform/internal/backend/remote-state/s3 0.507s ```
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 |
There was a problem hiding this 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
Thanks for the updates @bschaatsbergen! 👍 |
Clarify S3 permissions when using S3-native state locking.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚀
There was a problem hiding this 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>
use_lockfile
, as S3-native state locking is now stable and no longer considered experimental.