Currently if you provide a connectors 'core tables' in the schema config, it will successfully apply, but then if you do another plan/apply the Fivetran provider thinks the 'core tables' don't exist and attempt to apply them again.
This is because the underlying Fivetran API doesn't return 'core tables' when Terraform does the refresh.
Is there a way to support this scenario by either having Fivetran's API return Core Tables, or the Fivetran Terraform provider filtering out the Core Tables in the schema config? Or maybe something else?
Currently if you provide a connectors 'core tables' in the schema config, it will successfully apply, but then if you do another plan/apply the Fivetran provider thinks the 'core tables' don't exist and attempt to apply them again.
This is because the underlying Fivetran API doesn't return 'core tables' when Terraform does the refresh.
Is there a way to support this scenario by either having Fivetran's API return Core Tables, or the Fivetran Terraform provider filtering out the Core Tables in the schema config? Or maybe something else?