union_feature

[fivetran-reneeli]

Are you a current Fivetran customer?

Internal What change(s) does this PR introduce?

• Bring the source relation column downstream from the addition of the union feature
• Downstream changes from introducing the pricing source table which may replace the plan table depending on whether customer migrated to the Price API (some column names have changed in stripe__invoice_line_items)
• prefix variables with "stripe__" so they may be used globally

Did you update the CHANGELOG?

• [x] Yes

Does this PR introduce a breaking change?

• [x] Yes (please provide breaking change details below.)
• [ ] No (please provide an explanation as to how the change is non-breaking below.) Will need to refresh for this new field Did you update the dbt_project.yml files with the version upgrade (please leverage standard semantic versioning)? (In both your main project and integration_tests)
• [x] Yes

Is this PR in response to a previously created Bug or Feature Request

• [ ] Yes, Issue/Feature [link bug/feature number here]
• [x] No

How did you test the PR changes?

• [x] BuildKite
• [ ] Local (please provide additional testing details below)

Select which warehouse(s) were used to test the PR

• [x] BigQuery
• [x] Redshift
• [x] Snowflake
• [x] Postgres
• [x] Databricks
• [ ] Other (provide details below)

Provide an emoji that best describes your current mood

:dancer: **Feedback** We are so excited you decided to contribute to the Fivetran community dbt package! We continue to work to improve the packages and would greatly appreciate your [feedback](https://www.surveymonkey.com/r/DQ7K7WW) on our existing dbt packages or what you'd like to see next.

[fivetran-reneeli]

@fivetran-jamie so this is ready for review save for the error on databricks which i think is related to how i added null to price_id and plan_id in stg_stripe__pricing in the opposite source table CTEs as an additional field, to help the unique tests pass in the stg_stripe__pricing. So I'm still thinking through how to go about this

[fivetran-reneeli]

looks pretty good to me! just spotted a couple of places where we need to update the price variable name (though i suppose this will be merged with the other PR where you already did that 🤷 )

Thanks @fivetran-jamie yeah it doesn't hurt, I added your changes in 👍