Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature/q3 2023 updates #69

Merged
merged 48 commits into from
Oct 18, 2023
Merged

Feature/q3 2023 updates #69

merged 48 commits into from
Oct 18, 2023

Conversation

fivetran-reneeli
Copy link
Contributor

@fivetran-reneeli fivetran-reneeli commented Aug 31, 2023

PR Overview

This PR will address the following Issue/Feature: n/a

This PR will result in the following new package version: v 11

Significant updates to our Stripe package for Q3 2023.

Please detail what change(s) this PR introduces and any additional information that should be known during the review of this PR:

  • Addition of new Stripe report end models, plus updates to the balance transaction model
  • Additional of new fields

PR Checklist

Basic Validation

Please acknowledge that you have successfully performed the following commands locally:

  • dbt compile
  • dbt run –full-refresh
  • dbt run
  • dbt test
  • dbt run –vars (if applicable)

Before marking this PR as "ready for review" the following have been applied:

  • [n/a] The appropriate issue has been linked and tagged
  • You are assigned to the corresponding issue and this PR
  • BuildKite integration tests are passing

Detailed Validation

Please acknowledge that the following validation checks have been performed prior to marking this PR as "ready for review":

  • You have validated these changes and assure this PR will address the respective Issue/Feature.
  • You are reasonably confident these changes will not impact any other components of this package or any dependent packages.
  • You have provided details below around the validation steps performed to gain confidence in these changes.

Confirm that these additions appear in the target schema when run

Standard Updates

Please acknowledge that your PR contains the following standard updates:

  • Package versioning has been appropriately indexed in the following locations:
    • indexed within dbt_project.yml
    • indexed within integration_tests/dbt_project.yml
  • CHANGELOG has individual entries for each respective change in this PR
  • [n/a] README updates have been applied (if applicable)
  • DECISIONLOG updates have been updated (if applicable)
  • Appropriate yml documentation has been added (if applicable)

dbt Docs

Please acknowledge that after the above were all completed the below were applied to your branch:

  • docs were regenerated (unless this PR does not include any code or yml updates)

If you had to summarize this PR in an emoji, which would it be?

💃

Copy link
Contributor

@fivetran-joemarkiewicz fivetran-joemarkiewicz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fivetran-reneeli thanks for working through these changes. It seems that the most significant updates have been made to the balance transactions model which I can see being valuable to all users, not just the ones who will take advantage of these new reports!

I do have a number of requests for you to review and make appropriate updates.

Some major ones include my thoughts of renaming the fields in the staging models as opposed to the end model for consistency and allowing the focus of the transform models to be used for transformation purposes and not renaming. This also follows our intention of the source package. Following discussion with @fivetran-reneeli we will instead do the alias renaming in the final select statement. Updating the source will cause major scope creep although that is the preferred. Possibly we can open FR to make this update in the future.

Additionally, I wonder if we can consolidate the payout enhanced model with the balance transaction since they are almost identical. I would like to discuss those two in more detail before you move forward with updates.

See my other comments below and let me know if you have any questions. Thanks!

CHANGELOG.md Outdated Show resolved Hide resolved
README.md Show resolved Hide resolved
models/stripe__balance_transactions.sql Outdated Show resolved Hide resolved
CHANGELOG.md Show resolved Hide resolved
models/intermediate/int_stripe__payout_enhanced.sql Outdated Show resolved Hide resolved
models/stripe.yml Show resolved Hide resolved
models/stripe.yml Show resolved Hide resolved
models/stripe.yml Show resolved Hide resolved
models/stripe.yml Show resolved Hide resolved
models/stripe__balance_transactions.sql Show resolved Hide resolved
Copy link
Contributor

@fivetran-joemarkiewicz fivetran-joemarkiewicz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fivetran-reneeli thanks for making these updates and the new models are looking really good! I just have a few final comments (see the previous comments for any unresolved ones that should be addressed as well).

Once these updates are applied, be sure to address the source package review notes and then regen the docs. This should then be good to roll out!

Lastly you may need to use a new schema for integration tests as it looks like the Snowflake schema has conflicting role permissions now and is resulting in failed buildkite jobs.

CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
Copy link
Contributor

@fivetran-joemarkiewicz fivetran-joemarkiewicz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks so much for working on these updates @fivetran-reneeli. This looks good to go to release review!

CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
packages.yml Outdated
Comment on lines 2 to 7
# version: [">=0.9.0", "<0.10.0"]

- git: https://github.com/fivetran/dbt_stripe_source.git
revision: feature/q3-2023-updates
warn-unpinned: false
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bumping this reminder before merge

@fivetran-reneeli fivetran-reneeli merged commit af98ad9 into main Oct 18, 2023
@fivetran-reneeli fivetran-reneeli deleted the feature/q3-2023-updates branch October 18, 2023 22:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants