Can we add `loader` to the dbt_sources model?

[alexfetterman]

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] We want to audit our source configuration (loader, freshness, etc) against other extraction/loading data we will be populating in another table. We need to have a field that contains the name of the loader as defined in dbt.

Describe the solution you'd like A clear and concise description of what you want to happen. In the dbt_sources model, I would like to have the loader field available.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered. We have looked for other packages that serve source fields up to a dbt model (dbt_artifacts, dbt_project_evaluator). None of them serve all of what we need.

Additional context Add any other context or screenshots about the feature request here.

Would you be willing to contribute this feature? Let us know if you're willing to contribute so that we'll be able to provide guidance. I would be happy to assist.

[haritamar]

Hi @alexfetterman ! Thank you for opening this issue and very sorry for the super long delay. We are currently doing some order in our Github issues and improving our process there.

This makes a lot of sense, and should actually be a relatively straightforward contribution. So please let me know if you'd like to help here and I can add more details.