fix: migrate custom config keys to config(meta={}) with legacy fallback - #30
Merged
Merged
Conversation
) All config.get()/config.require() calls for package-specific keys now check config.meta first, falling back to the top-level config for backward compatibility. Integration test models migrate to meta={...} syntax to exercise the new primary read path under dbt v2's strict schema validation. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
UnusedConfigKey(dbt1060) errors raised by dbt Core v2's strict schema validation, which rejects unrecognized top-levelconfig()keyscortex_agent/create.sql,cortex_mcp_server/create.sql,cortex_skill/create.sql,cortex_agent.sqlmaterialization) now read custom keys fromconfig.metafirst, then fall back to the legacyconfig.get()/config.require()so consuming projects on dbt-core 1.12 continue to work without changesconfig(meta={...})syntax to exercise the new primary read pathTest plan
dbt parseinintegration_tests/completes with zeroUnusedConfigKeyerrorsdbt compileoutput foragent_minimal,agent_versioned,atlassian_mcp_server,forecaster_skillmatches expected DDLdbt parse --use-v2-parserto confirm v2 compatibilityCloses #29
🤖 Generated with Claude Code