-
Notifications
You must be signed in to change notification settings - Fork 8.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resource aws_dms_endpoint - Conflict between extra_connection_attributes and s3_settings #19667
Comments
Likely related #19501 |
@MauriceBrg Thanks for raising this! This is an interesting looking diff problem. Have you had a chance to try v4.2.0? The |
@MauriceBrg After looking more carefully at your configuration, here are some points.
As you have it, your configuration will not work well. AWS is reportedly going to deprecate
Example Config Using resource "aws_dms_endpoint" "test" {
endpoint_type = "target"
engine_name = "s3"
endpoint_id = "dummy-endpoint"
s3_settings {
bucket_folder = "some/prefix"
bucket_name = aws_s3_bucket.test.id
cdc_path = "cdc"
data_format = "parquet"
date_partition_enabled = true
include_op_for_full_load = true
parquet_timestamp_in_millisecond = true
parquet_version = "parquet-2-0"
service_access_role_arn = aws_iam_role.test.arn
timestamp_column_name = "timestamp"
}
} |
This issue should be resolved in v4.59.0 by using |
This functionality has been released in v4.50.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! |
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. |
Terraform CLI and Terraform AWS Provider Version
Affected Resource(s)
Terraform Configuration Files
Debug Output
Note: I changed my Account ID and IAM Username, aside from that it's the plain output.
https://gist.github.com/MauriceBrg/9ea8a732379413d2c72b9028de439656
Panic Output
Expected Behavior
A terraform plan after a successful apply shouldn't find any differences.
Actual Behavior
The terraform plan after the apply wants to change the configuration of the DMS-S3-Endpoint in a way that would remove the bucket name and other vital configuration properties.
My guess:
There are two places in the resource to configure certain properties:
s3_settings
andextra_connection_attributes
.Some configurations can be made in both places, the problem seems to arise when you configure settings in the
extra_connection_attributes
that could be configured unders3_settings
. In that case thes3_settings
seem to be preferred and overwrite theextra_connection_attributes
. Interestingly only on updates, the initial creation works just fine.Steps to Reproduce
terraform apply -auto-approve
terraform plan
Important Factoids
None.
References
extra_connection_attributes
present when configured withs3_settings
#19501The text was updated successfully, but these errors were encountered: