Fix resolution message for S3/DynamoDB state checksum mismatch

[mschfh]

The current resolution message incorrectly suggests updating the DynamoDB value to the value already stored there, rather than to the calculated checksum of the S3 state file.

Draft CHANGELOG entry

BUG FIXES

• Fixed the digest value displayed for DynamoDB/S3 state checksum mismatches.

[hashicorp-cla]

All committers have signed the CLA.

[mschfh]

@jbardin Could someone please review this?

[crw]

Apologies, somehow I missed this (GitHub notifications seem to be a little flaky). I've notified the AWS provider team.

[mschfh]

@crw Thanks. Is there any update yet, I can't see any reviewers assigned to the PR?

[crw]

It has not been picked up yet for review. I can see this on their project board, so it is basically backlogged at the moment. I'll check in with them.

[jar-b]

LGTM 🎉

% TF_ACC=1 go test ./...

ok      github.com/hashicorp/terraform/internal/backend/remote-state/s3 146.752s

[jar-b]

Thanks for your contribution, @mschfh! 👍

[github-actions]

Reminder for the merging maintainer: if this is a user-visible change, please update the changelog on the appropriate release branch.

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.