dynamodb_table_item does not update after change is made

[sanp]

When I create a dynamodb item in terraform, it works fine. But when I then make a change to the item, the terraform apply succeeds, but the change does not take effect in the actual Dynamo table.

Terraform version

Terraform v0.13.4
+ provider registry.terraform.io/hashicorp/aws v3.11.0

Affected Resource

aws_dynamodb_table_item

Terraform Configuration Files

I am just using the official example on the resource page.

First apply:

resource "aws_dynamodb_table" "example" {
  name           = "example-name"
  read_capacity  = 10
  write_capacity = 10
  hash_key       = "exampleHashKey"

  attribute {
    name = "exampleHashKey"
    type = "S"
  }
}

resource "aws_dynamodb_table_item" "example" {
  table_name = aws_dynamodb_table.example.name
  hash_key   = aws_dynamodb_table.example.hash_key

  item = <<ITEM
{
  "exampleHashKey": {"S": "something"},
  "one": {"N": "11111"},
  "two": {"N": "22222"},
  "three": {"N": "33333"},
  "four": {"N": "44444"}
}
ITEM
}

If I run terraform apply, this produces the expected table, with all five columns.

Second apply:

If I then change the item configuration to:

resource "aws_dynamodb_table_item" "example" {
  table_name = aws_dynamodb_table.example.name
  hash_key   = aws_dynamodb_table.example.hash_key

  item = <<ITEM
{
  "exampleHashKey": {"S": "something"},
  "one": {"N": "11111"},
  "three": {"N": "33333"},
  "four": {"N": "44444"}
}
ITEM
}

and run an apply, no change is made in the table in AWS. All columns still exist.

Debug Output

After running the second apply:

aws_dynamodb_table.example: Refreshing state... [id=example-name]
aws_dynamodb_table_item.example: Refreshing state... [id=example-name|exampleHashKey||something|]

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # aws_dynamodb_table_item.example will be updated in-place
  ~ resource "aws_dynamodb_table_item" "example" {
        hash_key   = "exampleHashKey"
        id         = "example-name|exampleHashKey||something|"
      ~ item       = jsonencode(
          ~ {
                exampleHashKey = {
                    S = "something"
                }
                four           = {
                    N = "44444"
                }
                one            = {
                    N = "11111"
                }
                three          = {
                    N = "33333"
                }
              - two            = {
                  - N = "22222"
                } -> null
            }
        )
        table_name = "example-name"
    }

Plan: 0 to add, 1 to change, 0 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

aws_dynamodb_table_item.example: Modifying... [id=example-name|exampleHashKey||something|]
aws_dynamodb_table_item.example: Modifications complete after 0s [id=example-name|exampleHashKey||something|]

Apply complete! Resources: 0 added, 1 changed, 0 destroyed.

Expected Behavior

I expect the second terraform apply to update the dynamo table in AWS and remove the "two": {"N": "22222"} column from the table.

Actual Behavior

The terraform apply succeeds according to the output. However, the table in AWS is not updated. All original columns still exist in the table.

Steps to Reproduce

1. Run terraform apply using the first apply configuration.
2. Update the configuration to remove one of the items and run terraform apply a second time.

[sanp]

Can someone please respond to this -- I just upgraded to

Terraform v0.13.5
+ provider registry.terraform.io/hashicorp/aws v3.15.0

and am still seeing the same bug.

[ftaib]

I am also still seeing the same bug.

Terraform v1.0.2
on darwin_amd64
+ provider registry.terraform.io/hashicorp/aws v3.61.0

[github-actions]

This functionality has been released in v4.19.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

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