[Bug]: `aws_dynamodb_table_item`s created in a Global Table have spurious attributes added

[gdavison]

Terraform Core Version

N/A

AWS Provider Version

4.62.0

Affected Resource(s)

aws_dynamodb_table_item

Expected Behavior

When there are no changes to an aws_dynamodb_table_item in a Global Table, there should be no diff reported

Actual Behavior

When using "Legacy" (v2017.11.29) Global Tables, the replication engine adds the following attributes to each item (https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/globaltables_HowItWorks.html):

• aws:rep:deleting
• aws:rep:updatetime
• aws:rep:updateregion

These attributes should be ignored by the provider.

The provider reports a diff like the following:

  ~ resource "aws_dynamodb_table_item" "item" {
       id         = "doormat-configuration|key||ssh_sign_ttl_config|"
     ~ item       = jsonencode(
         ~ {
             - aws:rep:deleting     = {
                 - BOOL = false
               } -> null
             - aws:rep:updateregion = {
                  - S = "us-east-1"
                } -> null
              - aws:rep:updatetime   = {
                  - N = "1678818915.260001"
                } -> null
                # (1 unchanged element hidden)
            }
        )
        # (2 unchanged attributes hidden)
    }

Confirm that "Current" (v2019.11.21) Global Tables do not have a similar problem.

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

N/A

Steps to Reproduce

N/A

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

None

[github-actions[bot]]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[dpowley]

also seeing that this is a problem for global tables on v2017.11.29 and is not a problem for global tables on version v2019.11.21