Cannot reference same Dagster Asset Key in two DBT Sources about dagster HOT 2 CLOSED

Your use case is valid. A single computation in Dagster can produce multiple data assets at once.

However, the fact still stands that each data asset needs to be associated with a unique asset key. This is a framework constraint. Although this was working for you before, this was not valid behavior.

My recommendation for you would be:

• You use a @multi_asset to produce your data assets: https://docs.dagster.io/concepts/assets/multi-assets. Your data assets should have unique keys associated with them.
• For dagster-dbt specific documentation, you can check out https://docs.dagster.io/integrations/dbt/reference#upstream-dependencies for using @multi_asset with dbt sources.

from dagster.

I used a multi_asset to solve the issue, but what happens now is that dagster runs the dbt CLI command twice instead of once god knows why

from dagster.