r/aws_dms_endpoint: diff in extra_connection_attributes present when configured with s3_settings

[anGie44]

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

Affected Resource(s)

• aws_dms_endpoint

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_endpoint" "dms_endpoint" {
  endpoint_id                 = random_pet.p.id
  endpoint_type               = "target"
  engine_name                 = "s3"
  ssl_mode                    = "none"
  extra_connection_attributes = "addColumnName=true;cdcMaxBatchInterval=600;DataFormat=parquet;datePartitionEnabled=false;maxFileSize=1048576;parquetTimestampInMillisecond=true;timestampColumnName=DMS_LOAD_TIME;"
  s3_settings {
    bucket_folder = "testfolder"
    csv_delimiter = ","
    bucket_name = "mybucket"
    service_access_role_arn = aws_iam_role.iam_role.arn
    compression_type = "GZIP"
    csv_row_delimiter = " "
  }
  tags = {
    Name   = random_pet.p.id
    Update = "to-update"
    Remove = "to-remove"
  }
  depends_on = [aws_iam_role_policy.dms_s3_access]
}

Expected Behavior

• Subsequent terraform plan after successful creation should not show a diff in extra_connection_attributes

Actual Behavior

• terraform plan shows a diff

aws_dms_endpoint.dms_endpoint: Refreshing state... [id=sharing-poodle]

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # aws_dms_endpoint.dms_endpoint will be updated in-place
  ~ resource "aws_dms_endpoint" "dms_endpoint" {
      ~ extra_connection_attributes = "addColumnName=true;bucketFolder=testfolder;bucketName=mybucket;cdcMaxBatchInterval=600;compressionType=GZIP;csvDelimiter=,;csvRowDelimiter= ;DataFormat=parquet;datePartitionEnabled=false;maxFileSize=1048576;parquetTimestampInMillisecond=true;timestampColumnName=DMS_LOAD_TIME;" -> "addColumnName=true;cdcMaxBatchInterval=600;DataFormat=parquet;datePartitionEnabled=false;maxFileSize=1048576;parquetTimestampInMillisecond=true;timestampColumnName=DMS_LOAD_TIME;"
        id                          = "sharing-poodle"
        tags                        = {
            "Name"   = "sharing-poodle"
            "Remove" = "to-remove"
            "Update" = "to-update"
        }
        # (6 unchanged attributes hidden)

        # (1 unchanged block hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

Steps to Reproduce

1. terraform apply
2. terraform plan

References

• resource/dms_endpoint: add support for extraConnectionAttributes in create/read ops and handle diffs #16827
• Resource aws_dms_endpoint - Conflict between extra_connection_attributes and s3_settings #19667

[ewbankkit]

Maybe related:

• Add S3 Connection Attributes to DMS Endpoint #17591
• Add dms endpoint s3 attributes to keep format from changing to default on update #14620