fivetran/dbt_fivetran_log v2.2.0

v2.2.0 dbt_fivetran_log

on GitHub

PR #154 includes the following updates:

Breaking Change for dbt Core < 1.9.6

Note: This is not relevant to Fivetran Quickstart users.
Migrated freshness from a top-level source property to a source config in alignment with recent updates from dbt Core. This will resolve the following deprecation warning that users running dbt >= 1.9.6 may have received:

[WARNING]: Deprecated functionality
Found `freshness` as a top-level property of `fivetran_platform` in file
`models/src_fivetran_platform.yml`. The `freshness` top-level property should be moved
into the `config` of `fivetran_platform`.

IMPORTANT: Users running dbt Core < 1.9.6 will not be able to utilize freshness tests in this release or any subsequent releases, as older versions of dbt will not recognize freshness as a source config and therefore not run the tests.

If you are using dbt Core < 1.9.6 and want to continue running Fivetran Platform freshness tests, please elect one of the following options:

1. (Recommended) Upgrade to dbt Core >= 1.9.6
2. Do not upgrade your installed version of the fivetran_log package. Pin your dependency on v2.1.0 in your packages.yml file.
3. Utilize a dbt override to overwrite the package's fivetran_platform source and apply freshness via the old top-level property route. This will require you to copy and paste the entirety of the src_fivetran_platform.yml file and add an overrides: fivetran_log property.

Bug fixes

• Updated logic for identifying broken connections. Connection sync_end events having log_status = 'FAILURE', in addition to SEVERE event types, are now considered broken connections. (PR #155)

Under the Hood

• Updated the package maintainer PR template.

Contributors

• @felipecoxanet (PR #152)

Full Changelog: v2.1.0...v2.2.0