Salesforce connector pulls default schema and tables when connector is first created. This creates problems for us as we manage connector and schema with different terraform resources and deployment flows. 

Current behaviour:

When connector is first deployed, it pulls in "salesforce" schema along with all the tables. In our cause, it was 1638 tables which were showing up in Fivetran UI out of which 729 tables were enabled by default. 

When we run salesforce schema deployment via terraform's fivetran_connector_schema_config we see total enabled tables within salesforce schema to 55 (which is correct)

But when we destroy fivetran_connector_schema_config terraform resource, we would expect the total enabled tables to back to 729 but we still see 55 enabled tables. It looks like terraform destroy is not making any difference to salesforce schema object.   

This creates problems when we want to manage connector and schema separately via terraform automation. 

Expected behaviour:

When we deploy Salesforce connector, we don't want to see any schemas pulled in. We want to manage schemas via terraform fivetran_connector_schema_config resource. When we deploy schema resource via terraform, we want to pull in only tables which we are interested in (and not all). When we destroy terraform schema resource, all the tables within the schema should be deleted as well.  

Plugin version:
1.1.2 

To Reproduce: