-
Notifications
You must be signed in to change notification settings - Fork 25
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/pricing update 2 #50
Conversation
…n/dbt_fivetran_log into feature/pricing-update-2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good and thanks for your hard work on this update! I did have a few quick updates that we should apply before this can be approved.
- Minor update to the CHANGELOG. See comments in line
- Regenerate the dbt docs
- Version index seems off. Should it instead by
0.6.0
?
…n/dbt_fivetran_log into feature/pricing-update-2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The updates look great! Thanks so much @fivetran-reneeli 🙌
Remember that we will hold off merging this until later.
An update we will want to make with this before release is adopt a new methodology to incorporate BOTH amount and credits used in the final model instead of just doing either or. |
…n/dbt_fivetran_log into feature/pricing-update-2
Pull Request
Are you a current Fivetran customer?
Internal
What change(s) does this PR introduce?
Updates package to reflect to new pricing update and corresponding new
usage_cost
table existing in users on the new pricing model. See #44 for more.Did you update the CHANGELOG?
Does this PR introduce a breaking change?
Shouldn't impact users on older pricing model and for users on new pricing model this should be net new. But I updated the version by +0.1.0 since it's pretty big
Did you update the dbt_project.yml files with the version upgrade (please leverage standard semantic versioning)? (In both your main project and integration_tests)
Is this PR in response to a previously created Bug or Feature Request
How did you test the PR changes?
Select which warehouse(s) were used to test the PR
Provide an emoji that best describes your current mood
💃
Feedback
We are so excited you decided to contribute to the Fivetran community dbt package! We continue to work to improve the packages and would greatly appreciate your feedback on our existing dbt packages or what you'd like to see next.