This PR will result in the following new package version:
v1.3.0, as this will be batched with breaking change updates
Please detail what change(s) this PR introduces and any additional information that should be known during the review of this PR:
This creates a new model, fivetran_platform__user_audit (how do we feel about this name? i also considered audit_user_activity/user_activity_audit) to track user-triggered actions in fivetran connectors and destinations
We have added a new model, fivetran_platform__user_audit (source):
Each record represents a user-triggered action in your Fivetran instance. This model is intended for audit-trail purposes, as it can be very helpful when trying to trace a user action to a log event such as a schema change, sync frequency update, manual update, broken connection, etc.
This model builds off of this sample query from Fivetran's docs.
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 (if applicable) tested out user/destination_membership variable configs
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
[x] 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.
See Hex notebook linked in height task
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)
[ ] DECISIONLOG updates have been updated (if applicable)
[x] 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)
waiting to do so on release branch
If you had to summarize this PR in an emoji, which would it be?
PR Overview
This PR will address the following Issue/Feature: https://github.com/fivetran/dbt_fivetran_log/issues/89
This PR will result in the following new package version:
v1.3.0, as this will be batched with breaking change updates
Please detail what change(s) this PR introduces and any additional information that should be known during the review of this PR:
This creates a new model,
fivetran_platform__user_audit(how do we feel about this name? i also considered audit_user_activity/user_activity_audit) to track user-triggered actions in fivetran connectors and destinationsNew Model Alert 👶🏽
PR #98 includes the following update:
fivetran_platform__user_audit(source):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":
See Hex notebook linked in height task
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:
waiting to do so on release branch
If you had to summarize this PR in an emoji, which would it be?
🌚