📜 tldr; Op name collision with two dbt assets in the same repository dbt --- Hi there! We're testing out assets here and I found something that I'm not sure is intended. If we try to create two

dbt

assets using load_assets_from_dbt_project in the same repository we get an error like this. I suspected the culprit is here. The Op/Solid is always called

dbt_project

and so it collides. 🧪 Our use case (because we maybe are doing things the wrong way). We have a single dbt_project and we are creating basic pipelines with airbyte -> dbt assets. But since we want to select different models for each job we use the

select

parameter to do this. on one job

dbt_assets_from_somewhere = load_assets_from_dbt_project(
    project_dir=DBT_PROJECT_DIR,
    profiles_dir=DBT_PROJECT_DIR + "/profile",
    select="tag:really_cool_stuff"
)

and on another

dbt_assets_and_such = load_assets_from_dbt_project(
    project_dir=DBT_PROJECT_DIR,
    profiles_dir=DBT_PROJECT_DIR + "/profile",
    select="tag:tags_are_fun,tag:really_fun"
)

Breaking this into repositories fixes the issue but this jobs are pretty similar in scope. Please let me know if I can provide any relevant input to help :)

cc @owen

hi @Gabriel Montañola! thanks for the detailed bug report -- you nailed the source of the issue 🙂. I'll get this fixed for this week's release

Thank you @owen totally crushing those issues! I hope to contribute with some Pull Requests soon too 🙂

absolutely! we're always happy to have new contributors 😄

FYI we're already using airbyte + dbt assets together 🙂