bringing over changes to new branch

.circleci/config.yml

@@ -25,42 +25,6 @@ jobs:
             pip install -r integration_tests/requirements.txt
             mkdir -p ~/.dbt
             cp integration_tests/ci/sample.profiles.yml ~/.dbt/profiles.yml
-      - run:
-          name: "Run Tests - Spark"
-          command: |
-            . venv/bin/activate
-            echo `pwd`
-            cd integration_tests
-            dbt deps
-            dbt seed --target spark --full-refresh
-            dbt run --vars '{using_account_history_mode_active_records: true, using_opportunity_history_mode_active_records: true, using_user_role_history_mode_active_records: true, using_user_history_mode_active_records: true, salesforce__user_role_enabled: false}' --target spark --full-refresh
-            dbt test --vars '{salesforce__user_role_enabled: false}' --target spark
-            dbt run --target spark --full-refresh
-            dbt test --target spark
-      - run:
-          name: "Run Tests - Postgres"
-          command: |
-            . venv/bin/activate
-            echo `pwd`
-            cd integration_tests
-            dbt deps
-            dbt seed --target postgres --full-refresh
-            dbt run --vars '{using_account_history_mode_active_records: true, using_opportunity_history_mode_active_records: true, using_user_role_history_mode_active_records: true, using_user_history_mode_active_records: true, salesforce__user_role_enabled: false}' --target postgres --full-refresh
-            dbt test --vars '{salesforce__user_role_enabled: false}' --target postgres
-            dbt run --target postgres --full-refresh
-            dbt test --target postgres
-      - run:
-          name: "Run Tests - Redshift"
-          command: |
-            . venv/bin/activate
-            echo `pwd`
-            cd integration_tests
-            dbt deps
-            dbt seed --target redshift --full-refresh
-            dbt run --vars '{using_account_history_mode_active_records: true, using_opportunity_history_mode_active_records: true, using_user_role_history_mode_active_records: true, using_user_history_mode_active_records: true, salesforce__user_role_enabled: false}' --target redshift --full-refresh
-            dbt test --vars '{salesforce__user_role_enabled: false}' --target redshift
-            dbt run --target redshift --full-refresh
-            dbt test --target redshift
       - run:
           name: "Run Tests - Snowflake"
           command: |
@@ -92,3 +56,41 @@ jobs:
           key: deps2-{{ .Branch }}
           paths:
             - "venv"
+
+      - run:
+          name: "Run Tests - Postgres"
+          command: |
+            . venv/bin/activate
+            echo `pwd`
+            cd integration_tests
+            dbt deps
+            dbt seed --target postgres --full-refresh
+            dbt run --vars '{using_account_history_mode_active_records: true, using_opportunity_history_mode_active_records: true, using_user_role_history_mode_active_records: true, using_user_history_mode_active_records: true, salesforce__user_role_enabled: false}' --target postgres --full-refresh
+            dbt test --vars '{salesforce__user_role_enabled: false}' --target postgres
+            dbt run --target postgres --full-refresh
+            dbt test --target postgres
+
+      - run:
+          name: "Run Tests - Spark"
+          command: |
+            . venv/bin/activate
+            echo `pwd`
+            cd integration_tests
+            dbt deps
+            dbt seed --target spark --full-refresh
+            dbt run --vars '{using_account_history_mode_active_records: true, using_opportunity_history_mode_active_records: true, using_user_role_history_mode_active_records: true, using_user_history_mode_active_records: true, salesforce__user_role_enabled: false}' --target spark --full-refresh
+            dbt test --vars '{salesforce__user_role_enabled: false}' --target spark
+            dbt run --target spark --full-refresh
+            dbt test --target spark
+      - run:
+          name: "Run Tests - Redshift"
+          command: |
+            . venv/bin/activate
+            echo `pwd`
+            cd integration_tests
+            dbt deps
+            dbt seed --target redshift --full-refresh
+            dbt run --vars '{using_account_history_mode_active_records: true, using_opportunity_history_mode_active_records: true, using_user_role_history_mode_active_records: true, using_user_history_mode_active_records: true, salesforce__user_role_enabled: false}' --target redshift --full-refresh
+            dbt test --vars '{salesforce__user_role_enabled: false}' --target redshift
+            dbt run --target redshift --full-refresh
+            dbt test --target redshift

.github/ISSUE_TEMPLATE/config.yml

@@ -1,4 +1,7 @@
 contact_links:
+  - name: Provide feedback or request a new package to our dbt package team
+    url: https://www.surveymonkey.com/r/DQ7K7WW
+    about: Fill out our survey form to provide valuable feedback to the Fivetran team developing and maintaining the dbt packages.
   - name: Ask a question during our office hours
     url: https://calendly.com/fivetran-solutions-team/fivetran-solutions-team-office-hours
     about: Schedule time during the external office hours block with the Fivetran Analytics Engineering team for support
@@ -10,4 +13,4 @@ contact_links:
     about: Check out the dbt docs for all dbt related information
   - name: Hang out in dbt Slack
     url: https://www.getdbt.com/community/
-    about: Have a question or just want to chat with fellow data friends, join dbt Slack and hangout in the tools-fivetran channel with us!
+    about: Have a question or just want to chat with fellow data friends, join dbt Slack and hangout in the tools-fivetran channel with us!

.github/pull_request_template.md

@@ -1,4 +1,3 @@
-Pull Request
 **Are you a current Fivetran customer?** 
 <!--- Please tell us your name, title and company -->
 

CHANGELOG.md

@@ -1,3 +1,15 @@
+# dbt_salesforce_source v0.5.0
+🎉 Salesforce Package Updates 🎉
+
+We are updating the Salesforce package! To improve its utility, the changes include the following:
+## Features
+  - Bringing additional tables to create a new Contact Enhanced and Sales Velocity model as well as updating the Opportunity Enhanced model. ([#30](https://github.com/fivetran/dbt_salesforce_source/pull/30))
+  - Allowing formula fields to be added as passthrough columns. We added integration with the Salesforce Formula package by embedding the macro outputs as part of our staging models so that your custom formula fields can be included. ([#30](https://github.com/fivetran/dbt_salesforce_source/pull/30))
+  - Standardization updates ([#25](https://github.com/fivetran/dbt_salesforce_source/pull/25)):
+      - Updated formatting in our `sql` files.
+      - The README has been updated to reflect our rehaul of our documentation style to make it more straightforward. 
+      - Added `identifier` variable to each source to allow for more end-user customization on which table to pull from.
+
 # dbt_salesforce_source v0.4.2
 ## Fixes
 - Casts the `created_date` and `closed_date` fields within the `stg_salesforce__opportunity` model to a timestamp using the `dbt_utils.type_timestamp()` macro. This is needed for Redshift users that see these fields being synced as `timestamptz` as the downstream date functions do not work with the timestamptz datatype.