[Bug]: aws_dynamodb_table.table.stream_arn Changes Are Not Detected

[onajourney]

Terraform Core Version

v1.6.4

AWS Provider Version

v3.76.1

Affected Resource(s)

• aws_dynamodb_table

Expected Behavior

disable behaviour

set stream_enabled=false on a table

output "stream_arn" {
  value = aws_dynamodb_table.simple.stream_arn
}

should display no arn
resources that use this arn value should be thorn down (aws_lambda_event_source_mapping, aws_lambda_permission, aws_iam_role_policy)

re-enable behavior

set stream_enabled=true

output "stream_arn" {
  value = aws_dynamodb_table.simple.stream_arn
}

should display new arn
resources that use this arn value should be created (aws_lambda_event_source_mapping, aws_lambda_permission, aws_iam_role_policy)

Actual Behavior

disable behaviour

set stream_enabled=false on a table

output "stream_arn" {
  value = aws_dynamodb_table.simple.stream_arn
}

displays old stream arn
resources stay the same

re-enable behavior

set stream_enabled=true

output "stream_arn" {
  value = aws_dynamodb_table.simple.stream_arn
}

displays old arn
resources still point to old stream arn

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

https://gist.github.com/onajourney/fe4b34b6490fff19af9f862a0f84fbd7

Steps to Reproduce

deploy -> disable stream -> deploy -> re-enable stream -> deploy

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

Very likely related to:
#23364
#650
#13662
#12194

Would you like to implement a fix?

None

[github-actions]

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.

[RadJaz]

This issue can be closed. This particular bug was by resolved #27664 which was included in the 4.39.0 release of the AWS provider.

If anyone is experiencing the issue where updating stream_enabled does not cause terraform to detect a change in stream_arn, updating the AWS provider version to >=4.39.0 should resolve your issue.

There is a very similar issue (#42560) where the exact same behavior occurs, except is caused by changing the stream_view_type argument instead of stream_enabled. That bug is resolved by #42561.