[Bug] Lack of migration path from user configs defined in profiles.yml
to the 'flags' key in dbt_project.yml
#10402
Labels
bug
Something isn't working
Is this a new bug in dbt-core?
Current Behavior
Initially introduced with #9289 and released with dbt-core v1.8 (though I see from #9183 that it was also backported to 1.6 and 1.7), there isn't a viable migration path for moving from user configs defined in
profiles.yml
to the 'flags' key in dbt_project.yml.The current behavior is that if user configs ARE defined in
profiles.yml
and the 'flags' key is NOT defined dbt_project.yml, dbt will yield this warning:if user configs ARE defined in
profiles.yml
and the 'flags' key is ALSO defined indbt_project.yml
, dbt will yield this error:The issue is that, as mentioned in dbt's documentation,
profiles.yml
is often not part of the dbt project and so not version-controlled:For an organization to make this change, then, each member of the organization would need to update their
profiles.yml
simultaneously with the creation of theflags
key indbt_project.yml
in order to avoid a runtime error.Expected Behavior
My expectation is that setting both user configs defined in
profiles.yml
and the 'flags' key in dbt_project.yml would yield a deprecation warning, with the user config defined inprofiles.yml
being ignored in favor of the 'flags' key indbt_project.yml
. This would allow users to opt-in to the new behavior, as intended, instead of making this, effectively, a hard deprecation for any organization with more than one user.Steps To Reproduce
profiles.yml
:and a 'flags' key in
dbt_project.yml
dbt debug
)Relevant log output
No response
Environment
Which database adapter are you using with dbt?
snowflake
Additional Context
No response
The text was updated successfully, but these errors were encountered: