Using aws_dms_replication_task without replication_task_settings being provided

[dealweb723]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• 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
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform AWS Provider Version

• terraform 13.6
• hashicorp/aws 3.36

Affected Resource(s)

• aws_dms_replication_task

Terraform Configuration Files

Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.

resource "aws_dms_replication_task" "dms_rep_task" {
  migration_type            = "full-load-and-cdc"
  replication_instance_arn  = [remove for security reasons]
  replication_task_id       = "my-dms-task-id"
  source_endpoint_arn       = [remove for security reasons]
  table_mappings            = "{\"rules\":[{\"rule-type\":\"selection\",\"rule-id\":\"1\",\"rule-name\":\"1\",\"object-locator\":{\"schema-name\":\"%\",\"table-name\":\"%\"},\"rule-action\":\"include\"}]}"

  target_endpoint_arn       = [remove for security reasons]
}

Debug Output

Panic Output

Expected Behavior

Expected tf apply to be able to run multiple times without issue

Actual Behavior

• Running aws_dms_replication_task but without providing replication_task_settings as that is an optional setting per the doc (https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/dms_replication_task#replication_task_settings)
• Everything is created just fine after the first apply
• Run the same tf code again and still without the optional replication_task_settings and it fails. In looking at tf plan it shows that replication_task_settings is there and it plans to remove it. The tf apply fails with "Error: InvalidParameterCombinationException: No modifications were requested on the task"
• The work around is to add some dummy json to aws_dms_replication_task in the initial build and keep that in any builds onwards.

Steps to Reproduce

1. Run terraform apply
2. Rerun terraform apply

Important Factoids

References

• aws_dms_replication_task replication_task_settings always reports as needing modification #1513 aws_dms_replication_task replication_task_settings always reports as needing modification #1513
• AWS DMS Tasks fails with "Invalid task settings JSON" #9200 AWS DMS Tasks fails with "Invalid task settings JSON" #9200

[Sebor]

I've faced with the same issue.
it is necessary to use

  lifecycle {
    ignore_changes = [replication_task_settings]
  }

as dirty workaround

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