This PR upgrades dbt-core to 1.8.0 and dbt-athena-community to 1.8.1, which are the latest releases of both packages.
Based on the upgrade guide, it only seems like we need to make two changes:
Update requirements.txt to specify an install of dbt-core alongside dbt-athena-community
Rename the tests: attribute to data_tests: in all schema files that implement tests
Both of these changes are currently backwards-compatible with 1.7, so it's not strictly necessary for us to make them right now, but I figure we might as well do so anyway.
Note that even though I've replaced as many tests: instances as I could find, dbt is still outputting this warning when I run any command:
18:07:51 [WARNING]: Deprecated functionality
The `tests` config has been renamed to `data_tests`. Please see
https://docs.getdbt.com/docs/build/data-tests#new-data_tests-syntax for more
information.
I have a feeling that this warning is being caused by dbt_utils, which has not yet merged its release candidate. Since the old tests: attribute is still supported as an alias for data_tests:, and since I can't find any further instances of tests: in our code, I don't think it's a major problem.
This PR upgrades dbt-core to 1.8.0 and dbt-athena-community to 1.8.1, which are the latest releases of both packages.
Based on the upgrade guide, it only seems like we need to make two changes:
requirements.txtto specify an install ofdbt-corealongsidedbt-athena-communitytests:attribute todata_tests:in all schema files that implement testsBoth of these changes are currently backwards-compatible with 1.7, so it's not strictly necessary for us to make them right now, but I figure we might as well do so anyway.
Note that even though I've replaced as many
tests:instances as I could find, dbt is still outputting this warning when I run any command:I have a feeling that this warning is being caused by
dbt_utils, which has not yet merged its release candidate. Since the oldtests:attribute is still supported as an alias fordata_tests:, and since I can't find any further instances oftests:in our code, I don't think it's a major problem.Closes #438.