Releases: fivetran/dbt_stripe
v0.9.0 dbt_stripe
#56 includes the following changes:
π¨ Breaking Changes π¨:
stripe__subscription_line_items
has been removed. To recreate it, simply filterstripe__invoice_line_items
for wheresubscription_id
is not null.- The
stripe__weekly_overview
,stripe__quarterly_overview
, andstripe__monthly_overview
models have been removed as they can be recreated directly from thestripe__daily_overview
by rolling up the date grain. - The
stripe__invoice_line_item
andstripe__subscription_line_items
have been renamed tostripe__invoice_line_item_details
andstripe__subscription_details
. - Following the addition of the new
pricing
source table which may replace theplan
table depending on whether you migrated to the Price API (Stripe doc here.), the following columns instripe__invoice_line_items
have been updated. This package will draw the respective columns from theprice
object by default if it exists. However, if you still have and wish to keep usingplan
, you can setstripe__using_price
to False. For more please see the README
Previous Name | New Name |
---|---|
plan_is_active | price_plan_is_active |
plan_amount | price_plan_amount |
plan_interval | price_plan_interval |
plan_interval_count | price_plan_interval_count |
plan_nickname | price_plan_nickname |
plan_product_id | price_plan_product_id |
-
In addition,
stripe__plan_metadata
variable has been renamed tostripe__price_plan_metadata
-
Variables have been prefixed with
stripe__
so they can be used globally.
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 |
using_price | stripe__using_price |
- In the
stripe__subscription_details
model,start_date
has been updated tostart_date_at
to follow our standard naming practices.
π Feature Updates π
- Introducing the new model
stripe__invoice_details
. - Updated the models
stripe__daily_overview
with additional daily and rolling metrics. subscription_item_id
has been added to thestripe__invoice_line_items
model.- Added the ability to union datasets across different schemas or databases. A new column populating each model called
source_relation
will specify the source of each record.
For more information please refer to the README and stripe.yml
Full CHANGELOG: v0.8.0...v0.9.0
dbt_strirpe 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
andcurrent_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
dbt_stripe v0.7.3
Happy Thursday! π
This release of the dbt_stripe
package includes the following updates:
π Feature Updates
- Included the
currency
field within thestripe__invoice_line_items
model. (#44)
Contributors
Full Changelog: v0.7.2...v0.7.3
dbt_stripe v0.7.2
Happy Monday! π·
This release of the dbt_stripe
package includes the following updates:
π Feature Updates
- Databricks compatibility 𧱠(#44)
dbt_stripe v0.7.1
Happy Thursday π±
This release of the dbt_stripe
package includes the following updates:
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 ofdbt_stripe_source
. (#41)
dbt_stripe v0.7.0
Happy Thursday! π°
This release of the dbt_stripe
package includes the following updates:
π¨ Breaking Changes π¨
- Stripe connectors set up after February 09, 2022 no longer sync the
subscription
table; however, a newersubscription_history
table is synced. To account for this change a variablestripe__subscription_history
has been added to the package project to allow for users to define if their source contains thesubscription_history
table. (#37)- By default this variable is set to
false
. If you still have thesubscription
table, then there is no adjustment needed on your end. If you do have thesubscription_history
table then you will want to set the variable totrue
. - 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)
- By default this variable is set to
π Bug Fixes π
- Fix issue with timezone conversion in postgres by updating the
date_timezone
macro with postgres functionality. (#35) - Added Postgres support for the Stripe package. (PR #37)
Contributors
- @johnf (#35)
- @nachimehta (#37)
dbt_stripe 0.6.1
π Bug Fixes π
- #24: Updating docs to add
dbt_stripe
documentation in addition todbt_stripe_source
documentation. - #27: Updating
models/stripe__customer_overview.sql
to usemax
instead ofmin
for calculatingmost_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.
stripe 0.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 latestdbt_stripe_source
package has a dependency on the latestdbt_fivetran_utils
. Further, the latestdbt_fivetran_utils
package also has a dependency ondbt_utils
[">=0.8.0", "<0.9.0"].- Please note, if you are installing a version of
dbt_utils
in yourpackages.yml
that is not in the range above then you will encounter a package dependency error.
- Please note, if you are installing a version of
dbt_stripe v0.5.1
π New Feature π
This v0.5.1
release includes the following non-breaking changes. Please refer to the CHANGELOG for additional information.
Features
- Add functionality to include customer metadata in
stripe__customer_overview
. (#21) The customer metadata is passed in from thestg_stripe__customer
model in the Stripe source package.- For more information refer to the Stripe source package CHANGELOG
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!