[Bug]: aws_dms_replication_task forcing removal of CloudWatchLogStream on every run

[mitchellharvey97]

Terraform Core Version

1.5.7

AWS Provider Version

5.43

Affected Resource(s)

aws_dms_replication_task

Expected Behavior

Should be able to enable logging & not have to set the CloudWatchLogStream within the replication_task_settings object with 0 changes

Actual Behavior

Since upgrading to AWS Provider v5.42, terraform now wants to try and remove unset logging properties of CloudWatchLogGroup & CloudWatchLogStream. These are ReadOnly properties that cannot be modified or set so results in changes for every run

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

A very trimmed down version of the config to give the general idea

resource "aws_dms_replication_task" "dms" { for_each = var.dms_replication_task migration_type = each.value.migration_type replication_instance_arn = aws_dms_replication_instance.dms.replication_instance_arn replication_task_id = each.key replication_task_settings = file("${path.module}/dms-task-settings.json") source_endpoint_arn = aws_dms_endpoint.dms_source_endpoint[each.value.source].endpoint_arn table_mappings = jsonencode(local.dms_table_mappings[each.key]) start_replication_task = true target_endpoint_arn = aws_dms_endpoint.dms_target_endpoint[each.value.target].endpoint_arn }

dms-task-settings.json

{ "Logging": { "EnableLogging": true, "EnableLogContext": false, "LogComponents": [ { "Severity": "LOGGER_SEVERITY_DEFAULT", "Id": "TRANSFORMATION" }, { "Severity": "LOGGER_SEVERITY_DEFAULT", "Id": "SOURCE_UNLOAD" } ] }, }

Steps to Reproduce

Create a DMS replication task with logging enabled and provide a replication_task_settings object that does not contain the redonly fields of CloudWatchLogGroup & CloudWatchLogStream

Debug Output

No response

Panic Output

No response

Important Factoids

Believe this has been reintroduced in 5.42 as I can set the version back to 5.41 without an issue. This was first resolved in 2021 under PR 13476

References

https://github.com/hashicorp/terraform-provider-aws/pull/13476/files

Would you like to implement a fix?

No

[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.

[github-actions]

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.

[github-actions]

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