Skip to content

v0.9.0 dbt_stripe_source

Compare
Choose a tag to compare
@fivetran-reneeli fivetran-reneeli released this 31 Jan 17:06
· 93 commits to main since this release
b5b8423

PR #59 contains the following changes:

🚨 Breaking Changes 🚨

  • Variable names have been updated to contain the stripe prefix, allowing you to configure global variables while only affecting the Stripe package.
Previous Name New Name
using_invoices stripe__using_invoices
using_credit_notes stripe__using_credit_notes
using_payment_method stripe__using_payment_method
using_livemode stripe__using_livemode
using_invoice_line_sub_filter stripe__using_invoice_line_sub_filter
using_subscriptions stripe__using_subscriptions
using_subscription_history stripe__using_subscription_history
  • stg_stripe__plan has been changed to stg_stripe__price_plan. Following Stripe's migration from the Plan object to the Price object (Stripe doc here.), we have added a new variable stripe__using_price and macro does_table_exist that checks if the price table exists. This package uses price by default if it exists. However, if you still have and wish to keep using plan, you can set stripe__using_price to False. For more please see the README
  • stripe__plan_metadata variable has been renamed to stripe__price_plan_metadata
  • Stripe connectors set up after February 09, 2022 will use the subscription_history table, as they will no longer be syncing the subscription table. This package uses subscription_history by default if it exists. However, if you still have the subscription table and wish to use it instead, then set the stripe__using_subscription_history to False.

🎉 Feature Updates 🎉:

  • Added the Union ability to allow for multiple Stripe connectors. The new source_relation column in each staging model will specify where each record comes from. For more information please see the README #33
  • Added new price source table in addition to new stripe__using_price variable. Stripe migrated the Plan API to Price API (for more information, refer to their docs) so we recommend using the price table. The stripe__using_price variable and does_table_exist macro checks to see if you are indeed using the price table. If you plan on using the plan table instead you may toggle this to False. For more information on how to configure, refer to the README.
  • Added additional fields to the following models: stg_stripe__charge, stg_stripe__invoice, stg_stripe__invoice_line_item,stg_stripe__payment_method_card, stg_stripe__refund, stg_stripe__subscription.

For more please see the README

Full Changelog: v0.8.0...v0.9.0