Closed NickMUnlockHealth closed 6 months ago
Hey @NickMUnlockHealth!
I've checked our public documentation about S3 connector and found out that you need to use prefix
field to provide folder_path
for s3
connectors: https://fivetran.com/docs/rest-api/connectors/config#amazons3
I'm sorry about that inconsistency in our file connectors, but looks like it's historical thing...
Just update your config the following way:
resource "fivetran_connector" "this" {
group_id = data.fivetran_destination.this.id
service = "s3"
auth {
role_arn = aws_iam_role.this.arn
}
destination_schema {
name = "s3"
table = var.fivetran_destination_table
}
config {
bucket = var.s3_bucket
prefix = var.s3_prefix
on_error = var.fivetran_on_error
}
}
I've tested proposed solution and succesfully set Folder Path to desired value:
Describe the bug
To Reproduce Provide an example .tf configuration
Expected behavior Connector resource creates without error.
Logs & Output
Plugin version:
Additional context Connector works after manually adding in the folder path in the FiveTran UI, however the Terraform resource remains tainted.