feature/passthrough-addition

CHANGELOG.md

@@ -1,3 +1,6 @@
+# dbt_zendesk v0.8.3
+## Features
+- The `zendesk__ticket_enriched` and `zendesk__ticket_metrics` models now allow passthrough columns to be included through the use of the `zendesk__ticket_passthrough_columns` variable! ([#70](https://github.com/fivetran/dbt_zendesk/pull/70))
 # dbt_zendesk v0.8.2
 ## Fixes
 - It was brought to our attention that the `dbt_utils.date_trunc` macro only leverages the default arguments of the date_trunc function in the various warehouses. For example, `date_trunc` in Snowflake for the `week` argument produces the starting Monday, while BigQuery produces the starting Sunday. For this package, we want to leverage the start of the week as Sunday. Therefore, logic within the business metric intermediate models has been adjusted to capture the start of the week as Sunday. This was done by leveraging the `week_start` macro within the `dbt-date` package. ([#68](https://github.com/fivetran/dbt_zendesk/pull/68))

README.md

@@ -49,7 +49,15 @@ vars:
     zendesk_database: your_database_name
     zendesk_schema: your_schema_name 
 ```
+### Adding Passthrough Columns
+This package includes all source columns defined in the [Zendesk Source package](https://github.com/fivetran/dbt_zendesk_source) staging models to be present within the `zendesk__ticket_enriched` and `zendesk__ticket_metrics` models. However, you may also include your own custom columns to these two end models by leveraging our passthrough variable. 
+```yml
+# dbt_project.yml
 
+...
+vars:
+  zendesk__ticket_passthrough_columns: [account_custom_field_1, account_custom_field_2]
+```
 ### Tracking Ticket Field History Columns
 The `zendesk__ticket_field_history` model generates historical data for the columns specified by the `ticket_field_history_columns` variable. By default, the columns tracked are `status`, `priority`, and `assignee_id`.  If you would like to change these columns, add the following configuration to your `dbt_project.yml` file. Additionally, the `zendesk__ticket_field_history` model allows for tracking the specified fields updater information through the use of the `zendesk_ticket_field_history_updater_columns` variable. The values passed through this variable limited to the values shown within the config below. By default, the variable is empty and updater information is not tracked. If you would like to track field history updater information, add any of the below specified values to your `dbt_project.yml` file. After adding the columns to your `dbt_project.yml` file, run the `dbt run --full-refresh` command to fully refresh any existing models. 
 

dbt_project.yml

@@ -1,5 +1,5 @@
 name: 'zendesk'
-version: '0.8.2'
+version: '0.8.3'
 
 config-version: 2
 require-dbt-version: [">=1.0.0", "<2.0.0"]

integration_tests/dbt_project.yml

@@ -1,7 +1,7 @@
 config-version: 2
 
 name: 'zendesk_integration_tests'
-version: '0.8.2'
+version: '0.8.3'
 
 profile: 'integration_tests'
 

packages.yml

@@ -1,5 +1,8 @@
 packages:
-  - package: fivetran/zendesk_source
-    version: [">=0.6.0","<0.7.0"] 
+  # - package: fivetran/zendesk_source
+  #   version: [">=0.6.0","<0.7.0"] 
   - package: calogica/dbt_date
-    version: [">=0.5.0", "<0.6.0"]
+    version: [">=0.5.0", "<0.6.0"]
+  - git: https://github.com/fivetran/dbt_zendesk_source.git
+    revision: feature/passthrough-addition
+    warn-unpinned: false