We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently, if you have duplicate keys in your profiles.yml, dbt just uses the last one.
my_profile: ... my_profile: ...
This pattern - duplicated yaml keys that silently overwrite - is not one we want to continue to support.
We should throw a deprecation warning with associated telemetry for this in dbt-core v1.10, and then eventually remove support entirely.
v1.10
If you have duplicate top-level keys in profiles.yml - throw a deprecation warning.
profiles.yml
The text was updated successfully, but these errors were encountered:
Similarish - #5114
Sorry, something went wrong.
No branches or pull requests
Housekeeping
Short description
Currently, if you have duplicate keys in your profiles.yml, dbt just uses the last one.
This pattern - duplicated yaml keys that silently overwrite - is not one we want to continue to support.
We should throw a deprecation warning with associated telemetry for this in dbt-core
v1.10
, and then eventually remove support entirely.Acceptance criteria
If you have duplicate top-level keys in
profiles.yml
- throw a deprecation warning.The text was updated successfully, but these errors were encountered: