Support multiple dbt project roots in a single repo

[ammarchalifah-bolt]

We have a multi-project structure within a single dbt repo. Is it possible to set up multiple project root directories in a single .dbt-checkpoint.yml file?

[pgoslatara]

@ammarchalifah-bolt Do you mean a single .pre-commit-config.yaml file?

[louistransfer]

Hello,
I also have the exact same use case : I have a centralized "dbt" folder, each of them containing a store, e.g :

• dbt/store_a/target/manifest.json
• dbt/store_b/target/manifest.json
  etc

It would be ideal to be able to either have a configuration supporting multiple folders or to at least give a glob-like path to find the manifest.json, from a single .pre-commit-config.yaml. It could probably be added in the .dbt-checkpoint.yaml,
something like this :

Solution 1

version: 1
dbt-project-dirs: 
   store_a:	
      - dbt/store_a/target
   store_b:	
      - dbt/store_b/target

or

Solution 2

dbt-projects-glob: dbt/*/target

I know that this sound quite exotic, yet I believe that this dbt architecture could be more and more used as more people are advocating for multi-repo dbts (examples :

• https://discourse.getdbt.com/t/how-to-configure-your-dbt-repository-one-or-many/2121
• https://docs.getdbt.com/best-practices/how-we-mesh/mesh-2-structures )

Now I guess that the change could be quite tricky, yet it would help tremendously when an engineer modifies multiple identical marts for distinct companies to ensure that the commits are ok.