switch disable default config to enable default

.buildkite/scripts/run_models.sh

@@ -20,7 +20,7 @@ dbt seed --target "$db" --full-refresh
 dbt run --target "$db" --full-refresh
 dbt test --target "$db"
 ## UPDATE FOR VARS HERE, IF NO VARS, PLEASE REMOVE
-dbt run --vars '{lead_history_columns: ['first_name', 'lead_status', 'urgency', 'priority', 'relative_score', 'relative_urgency', 'demographic_score_marketing', 'behavior_score_marketing'], marketo__enable_campaigns: true, marketo__enable_programs: true, marketo__activity_delete_lead_enabled: false}' --target "$db" --full-refresh
-dbt test --target "$db" --vars '{lead_history_columns: ['first_name', 'lead_status', 'urgency', 'priority', 'relative_score', 'relative_urgency', 'demographic_score_marketing', 'behavior_score_marketing'], marketo__enable_campaigns: true, marketo__enable_programs: true, marketo__activity_delete_lead_enabled: false}' --target "$db"
+dbt run --vars '{lead_history_columns: ['first_name', 'lead_status', 'urgency', 'priority', 'relative_score', 'relative_urgency', 'demographic_score_marketing', 'behavior_score_marketing'], marketo__enable_campaigns: false, marketo__enable_programs: false, marketo__activity_delete_lead_enabled: false}' --target "$db" --full-refresh
+dbt test --target "$db" --vars '{lead_history_columns: ['first_name', 'lead_status', 'urgency', 'priority', 'relative_score', 'relative_urgency', 'demographic_score_marketing', 'behavior_score_marketing'], marketo__enable_campaigns: false, marketo__enable_programs: false, marketo__activity_delete_lead_enabled: false}' --target "$db"
 ### END VARS CHUNK, REMOVE IF NOT USING
 dbt run-operation fivetran_utils.drop_schemas_automation --target "$db"

CHANGELOG.md

@@ -1,3 +1,17 @@
+# dbt_marketo v0.13.0
+[PR #43](https://github.com/fivetran/dbt_marketo/pull/43) includes the following updates:
+
+## Breaking Change
+- Changes the default enable/disable config from `disable` to `enable` for the `marketo__enable_campaigns` and `marketo__enable_programs` variables since the Quickstart product can dynamically enable/disable such components. If you are not a Quickstart user nor are syncing the respective `campaign` or `program` tables, you must configure the variables accordingly. Disable the related models or fields by adding the following to your `dbt_project.yml` file:
+
+```yml
+vars:
+    marketo__enable_campaigns:   False      # Disable if Fivetran is not syncing the campaign table. This will disable the marketo__campaigns, marketo__programs, marketo__email_stats__by_campaign, marketo__email_stats__by_program models.
+    marketo__enable_programs:    False      # Disable if Fivetran is not syncing the program table. This will disable the marketo__programs and marketo__email_stats__by_program models.
+```
+
+Refer to the [README](https://github.com/fivetran/dbt_marketo?tab=readme-ov-file#step-4-enablingdisabling-models) for more details. 
+
 # dbt_marketo v0.12.1
 [PR #42](https://github.com/fivetran/dbt_marketo/pull/42) includes the following updates:
 

README.md

@@ -76,19 +76,14 @@ vars:
 For additional configurations for the source models, please visit the [Marketo source package](https://github.com/fivetran/dbt_marketo_source).
 
 ### Step 4: Enabling/Disabling Models
-This package takes into consideration tables that may not be synced due to slowness caused by the Marketo API.  By default the `campaign` and `program` related-models are disabled.  If you sync these tables, enable the modeling done by adding the following to your `dbt_project.yml` file:
-
+This package takes into consideration tables that may not be synced due to slowness caused by the Marketo API. By default the `campaign`, `program`, and `activity_delete_lead` tables are enabled. If you do not sync these tables, disable the related models or fields by adding the following to your `dbt_project.yml` file:
 ```yml
 vars:
-    marketo__enable_campaigns:   true      # Enable if Fivetran is syncing the campaign table
-    marketo__enable_programs:    true      # Enable if Fivetran is syncing the program table
+    marketo__enable_campaigns:   False      # Disable if Fivetran is not syncing the campaign table. This will disable the marketo__campaigns, marketo__programs, marketo__email_stats__by_campaign, marketo__email_stats__by_program models.
+    marketo__enable_programs:    False      # Disable if Fivetran is not syncing the program table. This will disable the marketo__programs and marketo__email_stats__by_program models.
+    marketo__activity_delete_lead_enabled:  false     # Disable if Fivetran is not syncing the activity_delete_lead table
 ```
 
-Alternatively, you may need to disable certain models. The below models can be disabled by adding them to your `dbt_project.yml` file:
-```yml
-vars:
-    marketo__activity_delete_lead_enabled:  false     # Disable if you do not have the activity_delete_lead table 
-```
 ### (Optional) Step 5: Additional configurations
 <details open><summary>Expand/Collapse details</summary>
 <br>

dbt_project.yml

@@ -1,5 +1,5 @@
 name: 'marketo'
-version: '0.12.1'
+version: '0.13.0'
 config-version: 2
 require-dbt-version: [">=1.3.0", "<2.0.0"]
 on-run-start: "{{ lead_history_columns_warning() }}"

integration_tests/dbt_project.yml

@@ -1,16 +1,12 @@
 name: 'marketo_integration_tests'
-version: '0.12.1'
+version: '0.13.0'
 profile: 'integration_tests'
 config-version: 2
 
 models:  
     +schema: "marketo_{{ var('directed_schema','dev') }}"  
 
 vars:
-    # enable when regenerating docs
-    # marketo__enable_campaigns: true
-    # marketo__enable_programs: true
-
     marketo_schema: marketo_integration_tests_6
     marketo_source:
         marketo_lead_identifier: "marketo_lead_data"

models/intermediate/marketo__email_stats__by_campaign.sql

@@ -1,4 +1,4 @@
-{{ config(enabled=var('marketo__enable_campaigns', False)) }}
+{{ config(enabled=var('marketo__enable_campaigns', True)) }}
 
 with email_sends as (
 

models/intermediate/marketo__email_stats__by_program.sql

@@ -1,4 +1,4 @@
-{{ config(enabled=var('marketo__enable_campaigns', False) and var('marketo__enable_programs', False)) }}
+{{ config(enabled=var('marketo__enable_campaigns', True) and var('marketo__enable_programs', True)) }}
 
 with email_sends as (
 

models/marketo__campaigns.sql

@@ -1,4 +1,4 @@
-{{ config(enabled=var('marketo__enable_campaigns', False)) }}
+{{ config(enabled=var('marketo__enable_campaigns', True)) }}
 
 with campaigns as (
 

models/marketo__email_sends.sql

@@ -28,7 +28,7 @@ with sends as (
     select *
     from {{ ref('marketo__unsubscribes__by_sent_email') }}
 
-{% if var('marketo__enable_campaigns', False) %}
+{% if var('marketo__enable_campaigns', True) %}
 
 ), campaigns as (
 
@@ -73,13 +73,13 @@ with sends as (
 
     select 
         booleans.*,
-        {% if var('marketo__enable_campaigns', False) %}
+        {% if var('marketo__enable_campaigns', True) %}
         campaigns.campaign_type,
         campaigns.program_id,
         {% endif %}
         email_templates.is_operational
     from booleans
-    {% if var('marketo__enable_campaigns', False) %}
+    {% if var('marketo__enable_campaigns', True) %}
     left join campaigns using (campaign_id)
     {% endif %}
     left join email_templates

models/marketo__programs.sql

@@ -1,4 +1,4 @@
-{{ config(enabled=var('marketo__enable_campaigns', False) and var('marketo__enable_programs', False)) }}
+{{ config(enabled=var('marketo__enable_campaigns', True) and var('marketo__enable_programs', True)) }}
 
 with programs as (
 

packages.yml

@@ -1,3 +1,7 @@
 packages:
-- package: fivetran/marketo_source
-  version: [">=0.12.0", "<0.13.0"]
+# - package: fivetran/marketo_source
+#   version: [">=0.13.0", "<0.14.0"]
+
+  - git: https://github.com/fivetran/dbt_marketo_source.git
+    revision: default_enable
+    warn-unpinned: false