Today in Fivetran you can only connect one dbt repository to a Fivetran Destination.  This may work well for companies who use a mono-repo, but I have found the mono-repo is not very common in the wild.

Additionally, each repo config can only have one "Default Schema", one set of environment variables, and one "target" i.e. `targe.name`.  While I'm very familiar with schema naming macros, custom schema names, etc., it is limiting to only have one default schema name for an entire destination.  For example, in dbt Cloud, my Development Environment has default schema name dbt_myname and my Production Deployment environments has a different schema name.  I would like Fivetran to execute both scenarios.  (Same thing goes for target, etc.  I would have to change this back and forth in Fivetran UI to test different `target.name` )

I foresee a solution that uses a hierarch or container structure like this:

- Fivetran Destination 1

    -  Git Repository 1

           -  Configuration / Environment 1

                     -  Transformations

           -  Configuration / Environment 2

                     -  Transformations

     -  Git Repository 2

             - etc

- Fivetran Destination 2

     - etc

I hope that makes sense!  Thanks for the consideration!