[Bug]: aws_dms_endpoint: Remove ignore_headers_row s3 setting

[YakDriver]

Terraform Core Version

1.3.7

AWS Provider Version

5.0.0

Affected Resource(s)

• aws_dms_endpoint

Expected Behavior

This setting should not be there

Actual Behavior

It is

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

resource "aws_dms_endpoint" "test" {
  endpoint_id                 = "appa"
  endpoint_type               = "target"
  engine_name                 = "s3"
  ssl_mode                    = "none"

  s3_settings {
    service_access_role_arn = aws_iam_role.iam_role.arn
    ...
    ignore_headers_row = 1
  }

  depends_on = [aws_iam_role_policy.dms_s3_access]
}

Steps to Reproduce

1. terraform apply

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

• aws_dms_endpoint.ignore_header_rows typo #28579

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.

[jar-b]

Closed by #30452, merged to main via #31392

[github-actions]

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