-
Notifications
You must be signed in to change notification settings - Fork 10.2k
fix: parse boolean env vars in S3 backend correctly #37940
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
fix: parse boolean env vars in S3 backend correctly #37940
Conversation
d1d6240 to
b62d97a
Compare
|
Thanks for this submission! The S3 backend is maintained by the AWS Provider team at HashiCorp, and IBM company. I have notified that team of your PR. Thanks again! |
|
@crw Thank you for getting the PR in the queue. Can we expedite this process? It has been a month since it's pending review. |
This is consistent with the `kind` used for previous breaking changes to S3 backend behavior.
jar-b
left a comment
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 -count=1 ./...
ok github.com/hashicorp/terraform/internal/backend/remote-state/s3 202.097s|
Thank you for the contribution, @vietcgi! 👍 I modified the changelog entry to an upgrade note to align with how previous breaking changes to S3 backend behavior have been documented. |
YakDriver
left a comment
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 🎉
Setting
AWS_USE_FIPS_ENDPOINT=falseincorrectly enables FIPS endpoints because the code treats any non-empty string as true.This fixes
boolAttrDefaultEnvVarOkto properly parse "true"/"false" (case-insensitive), matching AWS SDK behavior.Fixes #37601