bugfix/daylight-end-catch

.github/PULL_REQUEST_TEMPLATE/maintainer_pull_request_template.md

@@ -11,15 +11,20 @@
 ### Basic Validation
 Please acknowledge that you have successfully performed the following commands locally:
 - [ ] dbt run –full-refresh && dbt test
-- [ ] dbt run (if incremental models are present)
+- [ ] dbt run (if incremental models are present) && dbt test
 
 Before marking this PR as "ready for review" the following have been applied:
 - [ ] The appropriate issue has been linked, tagged, and properly assigned
 - [ ] All necessary documentation and version upgrades have been applied
+    <!--- Be sure to update the package version in the dbt_project.yml, integration_tests/dbt_project.yml, and README if necessary. -->
 - [ ] docs were regenerated (unless this PR does not include any code or yml updates)
 - [ ] BuildKite integration tests are passing
 - [ ] Detailed validation steps have been provided below
 
 ### Detailed Validation
 Please share any and all of your validation steps:
-<!--- Provide the steps you took to validate your changes below. -->
+<!--- Provide the steps you took to validate your changes below. -->
+
+### If you had to summarize this PR in an emoji, which would it be?
+<!--- For a complete list of markdown compatible emojis check our this git repo (https://gist.github.com/rxaviers/7360908)  --> 
+:dancer:

.github/workflows/auto-release.yml

@@ -0,0 +1,13 @@
+name: 'auto release'
+on:
+  pull_request:
+    types:
+      - closed
+    branches:
+      - main
+
+jobs:
+  call-workflow-passing-data:
+    if: github.event.pull_request.merged
+    uses: fivetran/dbt_package_automations/.github/workflows/auto-release.yml@main
+    secrets: inherit

.quickstart/quickstart.yml

@@ -0,0 +1,26 @@
+database_key: zendesk_database
+schema_key: zendesk_schema
+
+dbt_versions: ">=1.3.0" "<2.0.0"
+
+table_variables:
+  using_schedules:
+    - daylight_time
+    - schedule_holiday
+    - schedule
+    - ticket_schedule
+    - time_zone
+  using_domain_names:
+    - domain_name
+  using_user_tags:
+    - user_tag
+  using_ticket_form_history:
+    - ticket_form_history
+  using_organization_tags:
+    - organization_tag
+
+destination_configurations:
+  databricks:
+    dispatch:
+      - macro_namespace: dbt_utils
+        search_order: [ 'spark_utils', 'dbt_utils' ]

CHANGELOG.md

@@ -1,3 +1,19 @@
+# dbt_zendesk v0.13.1
+
+[PR #128](https://github.com/fivetran/dbt_zendesk/pull/128) includes the following changes:
+## Bug Fixes
+- The `int_zendesk__schedule_spine` model was updated to properly account for schedules that recognized daylight savings time (DST) at one point in time, and then stopped recognizing it at a later date.
+  - For example, the Hong Kong timezone originally recognized DST, but then stopped in 1979. The previous versions of this package only recorded the schedule business hours until 1979. This update addresses this bug.
+  - Please note, this update will only effect users leveraging schedules.
+
+## Under the Hood
+- Included auto-releaser GitHub Actions workflow to automate future releases.
+- Updated the maintainer PR template to resemble the most up to date format.
+- Included a `quickstart.yml` file to allow for automated Quickstart data model deployments.
+
+## Contributors
+- [@elijamuel](https://github.com/elijamuel) ([Issue #121](https://github.com/fivetran/dbt_zendesk/issues/121))
+
 # dbt_zendesk v0.13.0
 
 ## 🚨 Breaking Change (Snowflake users) 🚨

dbt_project.yml

@@ -1,5 +1,5 @@
 name: 'zendesk'
-version: '0.13.0'
+version: '0.13.1'
 
 
 config-version: 2

integration_tests/dbt_project.yml

@@ -1,7 +1,7 @@
 config-version: 2
 
 name: 'zendesk_integration_tests'
-version: '0.13.0'
+version: '0.13.1'
 
 profile: 'integration_tests'
 

models/intermediate/int_zendesk__schedule_spine.sql

@@ -82,6 +82,23 @@ with timezone as (
     from order_timezone_dt
     where daylight_offset_minutes is not null
 
+    union all
+
+    select
+        time_zone,
+        standard_offset_minutes as offset_minutes,
+
+        -- Get the latest daylight_end_utc time and set that as the valid_from
+        max(daylight_end_utc) as valid_from,
+
+        -- If the latest_daylight_end_time_utc is less than todays timestamp, that means DST has ended. Therefore, we will make the valid_until in the future.
+        cast( {{ dbt.dateadd('year', 1, dbt.current_timestamp_backcompat()) }} as date) as valid_until
+
+    from order_timezone_dt
+    group by 1, 2
+    -- We only want to apply this logic to time_zone's that had daylight saving time and it ended at a point. For example, Hong Kong ended DST in 1979.
+    having cast(max(daylight_end_utc) as date) < cast({{ dbt.current_timestamp_backcompat() }} as date)
+
 ), calculate_schedules as (
 
     select