Can anyone tell me what the ‘right’ way to propagate target config env vars to dbt’s profile is? I’ve manually modified the dbt profile in the past but any time I update Meltano (or reinstall the dbt plugin) it gets overwritten .. which leads me to believe I shouldn’t be editing that directly?

Hi, @andrew_stewart. You should feel safe to update/override the Meltano profile.yml file. I am opening a new issue to document this problem you are seeing. The 'files' bundle for dbt has this file's update setting to 'true', meaning it would override on new installs, but I think this should be 'false'. You can add this snippet to your own

meltano.yml

file with 'true' replaced with 'false' and that should stop the files from getting ovewritten in the future. src/meltano/core/bundle/discovery.yml · master · Meltano / Meltano · GitLab

hey hey hey, I’m not a complete newb 😛

Cc @taylor and @ken_payne In the new adapter-specific versions of profiles.yml, I think it's worth considering making 'false' the default when it comes to these being overridden.

yea

hey hey hey, I’m not a complete newb 😛

Sorry, sorry. 😅 Just aiming to be helpful, and also put the extra detail+context in case someone finds this issue later.

I started to wonder if I was running up against a best practice (like, nudging users to propagate the dbt profile config + target config from the same source.. which would totally make sense!)

I think that's probably why the default is the way it is today, yes. But I think our thinking on this is evolving... rather than Meltano attempting to fully-bake and fully-manage it, we are leaning towards a solid default for whichever adapter you choose, and then just a tiny bit of training on how to maintain it yourself for your own environment. Of note, a draft snowflake-specific dbt profiles.yml that does a single source, with three stage-specific targets ('prod', 'staging', and 'dev') to align with the default Meltano environments: • Add snowflake-specific config (!2) · Merge requests · Meltano / files-dbt-snowflake · GitLab And up for discussion is a new proposal for 'warehouses' definitions which then could pass through their config to the target and dbt alike: • Top-level 'warehouse' definition in `meltano.yml`. (#3343) · Issues · Meltano / Meltano · GitLab

Yeah, I remember you and I discussed the toplevel DW concept before