fix: filter dbt models to upload only current project

[cedric-orange]

When you are using some tools like dbt-loom, graph.nodes.values() returns nodes from multiples project.

dbt-loom works by fetching public model definitions from your dbt artifacts, and injecting those models into your dbt project.

The goal of this PR is to only retrieve nodes from the current project using project_name selection to avoid uploading of unnecessary information.

[michael-myaskovsky]

Thanks for your contribution!
Please add a flag for this behavior, after that I'll be able to merge.

[cedric-orange]

I haven't seen in contributing guide a section about flag. Could you explain to me what is required ?

[michael-myaskovsky]

Since it changes the behavior, we want it to be an option that the user actively chooses. Either by configuration, or by an argument that the program receives. With the default being set to the original behavior.

[cedric-orange]

This does not change current behavior.
But this protects against duplicates that are populated in the database when dbt-loom is used.

[github-actions]

This pull request is stale because it has been open for too long with no activity.
If you would like the pull request to remain open, please remove the stale label or leave a comment.

[elazarlachkar]

Hi @cedric-orange!

I'm sorry for the delayed response.
Your PR looks good to me and I would like to merge it, I just commented with one question.
Could you look at it, and also update your branch to the latest elementary-data:master for the CI to pass?

Also, is that relevant also to groups and metrics artifacts?

[elazarlachkar]

I'm not familiar with project_name, but noticed in the dbt docs that it is accessed using the context (context[project_name]). Does this work without it?