I am new to dbt and have the following problem statement: for a number of subsequent compilations generate the single documentation page that will contain information for all of them.

The reason for sequence of compilations is that in my data model one BigQuery dataset serves for one customer and most of the dbt models for each customer are nearly identical. So, one dbt model is created for all customers but how it should be compiled is controlled by a variable (customer) passed:

dbt docs generate --var 'customer: foo'
dbt docs generate --var 'customer: bar'

The problem with such an approach is that despite significant reduction of code that should be written each compilation overrides the documentation page created by the previous one.

I found a similar case, but there the single documentation page is generated for multiple projects. One of the mentioned approaches is to merge artifacts (config, manifest) from 'target' folder that are required for documentation. This approach looks quite tricky but even despite this fact after merge there will be a set of nodes with identical names (model is the same, but only the variable passed is different) which is currently prohibited.

Has anybody handled similar task? Thank you so much