[Bug]: #30885 introduced a new perpetual diff

[k-brooks]

Terraform Core Version

1.4.5

AWS Provider Version

4.65.0

Affected Resource(s)

aws_dms_replication_task

Expected Behavior

Specifying the EnableLogContext property in the replication task settings should not trigger a perpetual diff.

Actual Behavior

Specifying the EnableLogContext property in the replication task settings triggers a perpetual diff.

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

resource "aws_dms_replication_task" "example" {
      id                        = "example"
      replication_task_settings = jsonencode(
           {
              Logging  = {
                  EnableLogContext = false
                }
            }
        )
    }

Steps to Reproduce

1. Apply
2. Plan - see diff

Debug Output

No response

Panic Output

No response

Important Factoids

Introduced by #30885

References

#19883

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.

[johnathan99j]

I'm getting this on provider 4.67.0 as well

[gfysaris]

I have the same issue with
Terraform v1.2.2 on windows_amd64

• provider registry.terraform.io/hashicorp/aws v5.11.0

[jcourteauupgrade]

This seems tied to the version of the DMS replication instance for the task. I don't have any issues when it's 3.5.1, but I do on 3.4.7. It looks like EnableLogContext requires > 3.5.0 (docs; look for AWS DMS Context logging header). Well scratch that; I have different behaviour for two different 3.4.7 tasks now. Colour me confused.

[r-roos]

Also encountering this issue on Terrafrom v1.3.1 with AWS provider version: 5.17.0

Is there any known workaround which can be applied?

[yoni-yad2]

Waiting for a fix as well.
diffs always show up for historyTimeslotInMinutes + EnableLogContext

[rameshkumar20]

Same issue with us as well. Always showing historyTimeslotInMinutes + EnableLogContext as changed.
This lead to DMS task being modified everytime and impacts our CDC data capture effecting our production systems. Appreciate for early resolution.

[github-actions]

This functionality has been released in v5.32.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.