dbt_stripe_source v0.7.4

Happy Tuesday!

This release of the dbt_stripe_source package includes the following updates

Under the Hood

• The plan_interval field within the stg_stripe__plan model has been aliased within the get_plan_columns() macro to allow for more flexibility across warehouses. (#58)
• BuildKite testing has been added. (#58)

dbt_stripe_source v0.7.3

Happy Thursday! 📚

This release of the dbt_stripe_source package includes the following updates:

Feature Updates

• The period_start and period_end fields have been added to the stg_stripe__invoice model. (#51)

Contributors

• @lijol (#50)

Full Changelog: v0.7.2...v0.7.3

dbt_stripe_source v0.7.2

Happy Monday! 🛷

This release of the dbt_stripe_source package includes the following updates:

🎉 Feature Updates

• Databricks compatibility 🧱 (#47)

dbt_stripe_source v0.7.1

🎉 Documentation and Feature Updates

• Add timezone notation to timestamp column definition (#42)
• Addition of subscription ID in the stg_stripe__invoice model (#41)

Contributors

• mvtemple (#43)
• ashishk-de (#44)

dbt_stripe_source v0.6.0

Happy Thursday! 🍰

This release of the dbt_stripe_source package includes the following updates:

🚨 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 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.

Features

• Added Postgres support for the Stripe package (#39)

Contributors

• @nachimehta (#37)

dbt_stripe_source v0.5.1

Under the Hood

• Addresses a bug in which timestamp columns in the balance_transaction source table are brought in as timestamp with time zone on Redshift and Postgres, which caused downstream datatype errors. These columns are now always cast as timestamp without time zone in the staging balance_transaction model (#22).

stripe_source 0.5.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_fivetran_utils. 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_source v0.4.4

🎉 New Feature 🎉

This v0.4.4 release includes the following non-breaking changes. Please refer to the CHANGELOG for additional information.

Features

• Add customer metadata to the customer object.

Under the Hood

• Allow metadata passthrough functionality for the customer staging model. Please see the README for more details on how to pivot out metadata properties. (#30)

dbt_stripe_source v0.1.0 -> v0.4.4

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

Metdata Pivot to Columns

Happy Thursday!

This release includes the following feature addition to the Fivetran Shopify Source dbt package:

• Addition of the stripe__[table]_metadata variables which allow a user to specify the respective staging models to pivot our desired objects within the metadata field to their own columns. PR #28

Huge shout out to @sachams and @mnahkies for their help on getting this integrated into the package 🎉

Include Sub Invoice Line Records and Credit Note Models

Addition of the variable to include sub invoice line records as well as the addition of the credit note models.

Happy Friday! This release includes the following non-breaking changes:

• Addition of the stg_stripe__credit_note and stg_stripe__credit_note_line_item models. These are disabled by default, but can be enabled by setting the using_credit_notes variable as true.
• Addition of the using_invoice_line_sub_filter variable. This variable filters out sub type invoice lines. This was being performed in previous releases of this package, but some users have requested to include the sub type invoices. As such, this variable is enabled by default to filter out sub type invoice lines. If you would like to not filter these out then you may set the variable to false.

Huge shout out to @dimoschi for raising some great questions and contributing to this release! 🎉