Update legacy dbt dependency spec to cover future requirements #571
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.
Our legacy dbt integration laid out a bunch of optional dependencies
on dbt core 1.4 plus various adapter packages.
The integration plan for MetricFlow 0.200.0 involves a dependency
link with dbt core 1.6 in order to enable query execution through
dbt adapters and reading from dbt project metadata for parsing
the semantic manifest.
This commit removes the legacy dependency structures and adds a
temporary dependency on dbt core 1.5. For the purposes of our
current integration steps 1.5 is adequate, and at the moment the
1.6 beta releases do not appear to be published for all of the
adapters we want to test.