customer360 updates -- add customer.phone and remove filter on is_deleted

[fivetran-jamie]

PR Overview

This PR will address the following Issue/Feature:

• [Feature] don't filter out deleted customers + persist the is_deleted field in stg_stripe__customer #71
• [Feature] Persist phone column in stg_stripe__customer #70

This PR will result in the following new package version:

v0.11.0 -- breaking since users will now have deleted customers in their datasets

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

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:

• 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.

See height task

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
• 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) -- WILL REGEN AFTER APPROVAL

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

☎️

[fivetran-joemarkiewicz]

LGTM! With one CHANGELOG suggestion and request to regen docs

[fivetran-joemarkiewicz]

I would actually make this it's own "Breaking Changes" section at the very top to really call this out.

[fivetran-jamie]

updated

[fivetran-catfritz]

lgtm!