Skip to content

Latest commit

 

History

History
108 lines (90 loc) · 6.77 KB

CHANGELOG.md

File metadata and controls

108 lines (90 loc) · 6.77 KB
Raw

dbt_stripe v0.8.0

🚨 Breaking Changes 🚨:

PR #48 includes the following breaking changes:

  • Dispatch update for dbt-utils to dbt-core cross-db macros migration. Specifically {{ dbt_utils.<macro> }} have been updated to {{ dbt.<macro> }} for the below macros:
    • any_value
    • bool_or
    • cast_bool_to_text
    • concat
    • date_trunc
    • dateadd
    • datediff
    • escape_single_quotes
    • except
    • hash
    • intersect
    • last_day
    • length
    • listagg
    • position
    • replace
    • right
    • safe_cast
    • split_part
    • string_literal
    • type_bigint
    • type_float
    • type_int
    • type_numeric
    • type_string
    • type_timestamp
    • array_append
    • array_concat
    • array_construct
  • For current_timestamp and current_timestamp_in_utc macros, the dispatch AND the macro names have been updated to the below, respectively:
    • dbt.current_timestamp_backcompat
    • dbt.current_timestamp_in_utc_backcompat
  • Dependencies on fivetran/fivetran_utils have been upgraded, previously [">=0.3.0", "<0.4.0"] now [">=0.4.0", "<0.5.0"].
  • Updated README to include instructions on how to use metadata variable in cases of dictionary arguments. (#51)

dbt_stripe v0.7.4

🎉 Feature Updates

  • Included the subscription_item_id field within the stripe__invoice_line_items model. (#50)
  • BuildKite testing has been added. (#52)

Contributors

dbt_stripe v0.7.3

🎉 Feature Updates

  • Included the currency field within the stripe__invoice_line_items model. (#44)

Contributors

dbt_stripe v0.7.2

🎉 Feature Updates

  • Databricks compatibility 🧱 (#44)

dbt_stripe v0.7.1

Feature Updates 🎉

  • README updates for easier package navigation and understanding. (#41)

Under the Hood

  • Updating the package dependency to reference the proper [">=0.7.0", "<0.8.0"] version range of dbt_stripe_source. (#41)

dbt_stripe v0.7.0

🚨 Breaking Changes 🚨

  • Stripe connectors set up after February 09, 2022 no longer sync the subscription table; however, a newer subscription_history table is synced. To account for this change a variable stripe__subscription_history has been added to the package project to allow for users to define if their source contains the subscription_history table. (#37)
    • By default this variable is set to false. If you still have the subscription table, then there is no adjustment needed on your end. If you do have the subscription_history table then you will want to set the variable to true.
    • Similarly, if you have both tables, then I highly encourage you start leveraging the subscription_history source table in your package.
    • This package now points to the latest dbt_stripe_source package version which accounts for the above update. (#33 and #34)

🐞 Bug Fixes 🐞

  • #35: Fix issue with timezone conversion in postgres by updating the date_timezone macro with postgres functionality. @johnf
  • Added Postgres support for the Stripe package.
  • See PR #37

Contributors

dbt_stripe v0.6.1

🐞 Bug Fixes 🐞

  • #24: Updating docs to add dbt_stripe documentation in addition to dbt_stripe_source documentation.
  • #27: Updating models/stripe__customer_overview.sql to use max instead of min for calculating most_recent_sale_date.
  • #28: Updating models/stripe__customer_overview.sql to include "No Associated Customer" records.
    • This PR accounts for when a transaction may be tied to a customer_id that has not yet synced into the customers table due primarily due to a sync lapse between the tables; in which case, the customer_description field will be "No Associated Customer".
    • Each "No Associated Customers" record will be an individual row, since we can not predictably do any group bys due to the stripe__customer_metadata variable variability in both datatype and number of metadata fields.

dbt_stripe v0.6.0

🎉 dbt v1.0.0 Compatibility 🎉

🚨 Breaking Changes 🚨

  • Adjusts the require-dbt-version to now be within the range [">=1.0.0", "<2.0.0"]. Additionally, the package has been updated for dbt v1.0.0 compatibility. If you are using a dbt version <1.0.0, you will need to upgrade in order to leverage the latest version of the package.
    • For help upgrading your package, I recommend reviewing this GitHub repo's Release Notes on what changes have been implemented since your last upgrade.
    • For help upgrading your dbt project to dbt v1.0.0, I recommend reviewing dbt-labs upgrading to 1.0.0 docs for more details on what changes must be made.
  • Upgrades the package dependency to refer to the latest dbt_stripe_source. Additionally, the latest dbt_stripe_source package has a dependency on the latest dbt_fivetran_utils. Further, the latest dbt_fivetran_utils package also has a dependency on dbt_utils [">=0.8.0", "<0.9.0"].
    • Please note, if you are installing a version of dbt_utils in your packages.yml that is not in the range above then you will encounter a package dependency error.

dbt_stripe v0.5.1

Features

  • Add functionality to include customer metadata in stripe__customer_overview. (#21) The customer metadata is passed in from the stg_stripe__customer model in the Stripe source package.

dbt_stripe v0.1.0 -> v0.5.0

  • Refer to the relevant release notes on the Github repository for specific details for the previous releases. Thank you!