Update partition logic with source relation

[fivetran-avinash]

PR Overview

This PR will address the following Issue/Feature: dbt_shopify_source issue #77

This PR will result in the following new package version: dbt_shopify v0.10.1

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

🐛 Bug Fixes 🪛

• Added source_relation to the partition_by clauses that determine the customer_index in the int_shopify__customer_email_rollup table.

🚘 Under The Hood 🚘

• Included auto-releaser GitHub Actions workflow to automate future releases.
• Added additional casting in seed dependencies for above models integration_tests/dbt_project.yml to ensure local testing passed on null cases.

PR Checklist

Basic Validation

Please acknowledge that you have successfully performed the following commands locally:

• dbt compile
• dbt run –full-refresh
• [NA] dbt run
• dbt test
• [NA] 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.

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
• [NA] README updates have been applied (if applicable)
• [NA] DECISIONLOG updates have been updated (if applicable)
• [NA] 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)

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

🏃🏽‍♂️

[fivetran-joemarkiewicz]

@fivetran-avinash thanks for working on these PRs! This generally looks good but I have a few requests and to make this a breaking change. Let me know if you have any questions!

[fivetran-joemarkiewicz]

Reminder to swap before merge

[fivetran-avinash]

@fivetran-joemarkiewicz PR should be ready for re-review. Buildkite changes are on non-model/yml files.

[fivetran-joemarkiewicz]

Approved with one comment and reminder to update the package deps.

[fivetran-joemarkiewicz]

Same note from the source, let's remove the bit about the full refresh as it is not necessary for these models.

Suggested change

	- Added `source_relation` to the `partition_by` clauses that determine the `customer_index` in the `int_shopify__customer_email_rollup` table. If the user is leveraging the union feature, this could change data values, so would recommend a `dbt run --full-refresh` in this case.
	- Added `source_relation` to the `partition_by` clauses that determine the `customer_index` in the `int_shopify__customer_email_rollup` table. If the user is leveraging the union feature, this could change data values.

[fivetran-catfritz]

lgtm!