This PR will address the following Issue/Feature: FR #96
This PR will result in the following new package version:v0.9.1
This is simply a documentation and under the hood update based on the updates within PR #104 from the source package. As such, no breaking updates will be reflected.
Please detail what change(s) this PR introduces and any additional information that should be known during the review of this PR:
This PR mainly includes documentation around the newly added hubspot_using_filtered_events variable (true by default) that changes the behavior of the stg_hubspot__email_event staging model to filter out filtered events if the variable is set to false. Please see PR #104 for more details around the upstream changes.
PR Checklist
Basic Validation
Please acknowledge that you have successfully performed the following commands locally:
[X] dbt compile
[X] dbt run –full-refresh
[X] dbt run
[X] dbt test
[X] dbt run –vars '{hubspot_using_filtered_events: false}'
Before marking this PR as “ready for review” the following have been applied:
[X] The appropriate issue has been linked and tagged
[X] 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”:
[X] You have validated these changes and assure this PR will address the respective Issue/Feature.
[X] You are reasonably confident these changes will not impact any other components of this package or any dependent packages.
[X] You have provided details below around the validation steps performed to gain confidence in these changes.
Please see PR #104 for the validation steps taken to ensure the changes are behaving as expected in the source. With comfort around these changes, I feel the downstream implications will behave the same and as intended.
Standard Updates
Please acknowledge that your PR contains the following standard updates:
Package versioning has been appropriately indexed in the following locations:
[X] indexed within dbt_project.yml
[X] indexed within integration_tests/dbt_project.yml
[X] CHANGELOG has individual entries for each respective change in this PR
[X] README updates have been applied (if applicable)
[N/A] DECISIONLOG updates have been updated (if applicable)
[N/A] 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:
[X] 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?
PR Overview
This PR will address the following Issue/Feature: FR #96
This PR will result in the following new package version:
v0.9.1This is simply a documentation and under the hood update based on the updates within PR #104 from the source package. As such, no breaking updates will be reflected.
Please detail what change(s) this PR introduces and any additional information that should be known during the review of this PR:
This PR mainly includes documentation around the newly added
hubspot_using_filtered_eventsvariable (true by default) that changes the behavior of thestg_hubspot__email_eventstaging model to filter out filtered events if the variable is set tofalse. Please see PR #104 for more details around the upstream changes.PR Checklist
Basic Validation
Please acknowledge that you have successfully performed the following commands locally:
Before marking this PR as “ready for review” the following have been applied:
Detailed Validation
Please acknowledge that the following validation checks have been performed prior to marking this PR as “ready for review”:
Please see PR #104 for the validation steps taken to ensure the changes are behaving as expected in the source. With comfort around these changes, I feel the downstream implications will behave the same and as intended.
Standard Updates
Please acknowledge that your PR contains the following standard updates:
dbt Docs
Please acknowledge that after the above were all completed the below were applied to your branch:
If you had to summarize this PR in an emoji, which would it be?
📧