[POP-7487] Add materialize adapter for dbt 1.0+ #3
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.
PR adds the materialize adapter as another thing we support for our dbt builds. dbt-materialize is unique in that it requires dbt-postgres to also be installed, and so that necessitated altering how
build_requirements.txt
worked so that I could have a way to specify "extra" requirements for certain adapters. While I initially had a way to do this in the original bash script, I figured this was getting a bit too "hairy" in terms of complex bash scripting and that it'd be hard to maintain in the future, that I also went ahead and rewrote the script to python. It ended up a bit longer, but it's far cleaner and I think easier to edit for other people, especially the lines determining what dependencies to include or not.Note, while dbt-materialize has versions available for
0.20.0
and0.21.0
, they used exact version matching against dbt-postgres (sodbt-materialize==0.21.0
requireddbt-postgres==0.21.0
), which would necessitate downgrading the version ofdbt-postgres@^0.21.1
we use. Given that I'm not sure the ramifications of that, and that these versions are years old and very much EOL, I figured fine to not support them unless someone explicitly asks and we can revisit then. We already also have precedent of some adapters only support 1.0+ (athena).