Update/rename package

[fivetran-jamie]

PR Overview

This PR will address the following Issue/Feature:

height task T-390568 https://github.com/fivetran/dbt_fivetran_log/issues/83

This PR will result in the following new package version:

considering we are renaming the package, v1.0.0?

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

• updates the fivetran_log prefix on all variables and models to fivetran_platform
• updates the default build schema suffixes to be _stg_fivetran_platform and _fivetran_platform
• changes the actual source name to fivetran_platform
• updates README accordingly
• adds missing documentation for _fivetran_synced in some sources
• updates incremental strategy for the audit table model
  • [x] where should we document this and tell people to run full refreshes every so often?
• adds incremental runs to Buildkite
• removes freshness tests from tables that probably don't update that often -- went somewhat rogue here but our tests are probably too strict
• totally removes anything related to the account_membership table which was deprecated - https://github.com/fivetran/dbt_fivetran_log/issues/83

what this does NOT do:

• change docs links
• change the actual package project name (as this is what dbt hub looks at)
• change the default schema

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)

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.

ran the two versions of the package simultaneously (since they have different project + model names). I looked at various models, but here I will focus on the audit table model, since i updated the the Bigquery + Spark incremental strategy for that model

1. ran a full refresh and spot checked different tables + connectors, but here are the total aggregates compared

   

2. ran an incremental run

   

everything checks out there -- should i validate any other way.. ?

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)
• [x] 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:

• [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?

📛

[fivetran-jamie]

@fivetran-joemarkiewicz added your changes! also for validation, i added some extra lines to the seed file

So, running before adding new dates:

I then add these new rows to the log seed file to simulate a sync of the media_insights table the next day (2021-12-10)

i dbt seed --full-refresh

i perform an incremental run, resulting in the following expected output (a new record for media_insights)