Hello, I am affected by a peculiar problem with potential easy solution (which I could write and propose as a PR, but wanted to hear community opinion about it first) - I ingest some datasets through snowflake connector with configured platform_instance option. Then I ingest some lineage which refers to the snowflake datasets using a DBT connector - the problem is DBT connector does not use platform_instance setting (it can be set but it is not used in the code) - is it intentional for DBT connector to not add platform_instance to ingested datasets? The change required here is a one-liner (out of curiosity I changed and then tested - ingested DBT lineage as expected with platform_instance) - would you accept PR introducing platform_instance to DBT connector or is it somehow against your vision for DBT?

I have found a couple of PRs related to this from @green-football-43791 : 1. https://github.com/datahub-project/datahub/pull/4926 feat(dbt): enable data platform instance on dbt #4926 This seems to be solving our request 👍. 2. https://github.com/datahub-project/datahub/pull/5028 fix(dbt): dont set platform instances for sources #5028 This one is removing the

platform_instance

for the source dataset when setting up the UpstreamLineage, which sounds wrong to me 🤔 Gabe, could you please confirm the status of the

platform_instance

feature for dbt connector and specially why the need for removing the

platform_instance

for the source in the UpstreamLineage? Thanks