v1.3.0 dbt_fivetran_log

🚨 Breaking Changes 🚨

• Deprecated the transformation and trigger_table source tables and any downstream transforms. These tables only housed information on Fivetran Basic SQL Transformations, which were sunset last year (PR #96).
  • The entire fivetran_platform__transformation_status end model has therefore been removed.
  • As they are now obsolete, the fivetran_platform_using_transformations and fivetran_platform_using_triggers variables have been removed.

👶🏽 New Model Alert 👶🏽

• We have added a new model, fivetran_platform__audit_user_activity (PR #98):
  • Each record represents a user-triggered action in your Fivetran instance. This model is intended for audit-trail purposes, as it can be very helpful when trying to trace a user action to a log event such as a schema change, sync frequency update, manual update, broken connection, etc.
  • This model builds off of this sample query from Fivetran's docs.

🪲 Bug Fixes 🪲

• Tightened incremental logic in fivetran_platform__audit_table, which was seeing duplicates on incremental runs (PR #97).
  • If you are seeing uniqueness test failures on the unique_table_sync_key field, please run a full refresh before upgrading to this version of the package.

🛠 Under the Hood 🛠

• Added a dependency on the dbt_date package (PR #98):

- package: calogica/dbt_date
  version: [">=0.9.0", "<1.0.0"]

Full Changelog: v1.2.0...v1.3.0