Dirk Avery

After looking at this more, this is resolved by using the `aws_dms_s3_endpoint` resource with the `aws_dms_replication_task` resource. We apologize for the inconvenience of switching resources but hopefully it is better...

**NOTE:** I cannot reproduce this error using **Terraform v1.5+/AWS provider v5.7+** after trying various configurations. Retry using a minimum of **Terraform v1.4.2/AWS provider v4.67.0** but preferably **Terraform v1.5.3+/AWS provider v5.8.0+**...

I tried this config to reproduce this specific issue. I got no errors. Here's my process to attempt to reproduce the problem: 1. `apply` config as is 2. remove `default_tags`...

Based on the age of this issue, I would say that at this point it needs to be thoroughly researched again to ensure it is still an issue. There may...

It has been over a year since anyone commented on this issue. I will be working to repro this and closing it if AWS and/or AWS provider changes have fixed...

I was able to reproduce this problem with this configuration: ```terraform data "aws_partition" "current" {} resource "aws_iam_role" "test" { name = "roletna" managed_policy_arns = ["arn:aws:iam::aws:policy/service-role/AWSLambdaBasicExecutionRole"] assume_role_policy = jsonencode({ Version =...

We will not fix this issue except with documentation updates. We won't fix this with provider code changes for these reasons: 1. The resources are acting as expected, managing what...

Changing `target_id` to a list would be a breaking change and require waiting until v5 of the AWS provider. However, perhaps a better solution would be to add a new...

FYI, Most used resources in the awscc provider: 1. awscc_chatbot_slack_channel_configuration 2. awscc_chatbot_microsoft_teams_channel_configuration Looks like @madhavvishnubhatta is on the exact right path with #37222

@thaJeztah I debugged this issue in a different project. For me, the cause was an initialized buffer having a starting size. When you `Write()` to the buffer, it _appends_ everything...