Triggers & Scheduling

triggers:
  - event: pull_request
    branches: ['main', 'develop']
    types: ['opened', 'synchronize', 'reopened']
    includes:
      - "models/**/*.sql"
      - "models/**/*.yml"
    auto_commit: false

name: pr_reviewer

triggers:
  - event: pull_request
    branches: ['main']
    types: ['opened', 'synchronize']
    includes:
      - "models/**"
      - "macros/**"

prompt: |
  Review this PR for dbt best practices and potential issues.
  Post your findings as a helpful PR comment.

triggers:
  - event: push
    branches: ['main']
    includes:
      - "**/*.sql"

name: post_merge_docs

triggers:
  - event: push
    branches: ['main']
    includes:
      - "models/**/*.sql"

prompt: |
  New models were merged to main. Update documentation for any 
  models that are missing descriptions or have outdated metadata.
  Create a PR with the documentation updates.

triggers:
  - event: scheduled
    cron: "0 9 * * 1"
    branches: ['main']
    includes:
      - "models/**"

name: weekly_audit

triggers:
  - event: scheduled
    cron: "0 9 * * 1"  # Every Monday at 9 AM UTC
    branches: ['main']

prompt: |
  Perform a weekly documentation audit:
  1. Check all models in models/marts/ for missing descriptions
  2. Calculate overall documentation coverage
  3. Send a summary report to #data-documentation on Slack

tools:
  include:
    - slack_tool

triggers:
  - event: airflow
    type: dag_run_failed
    includes:
      - "critical_pipeline"
      - "daily_refresh"

import requests

def notify_buster_on_failure(context):
    requests.post(
        "https://api.buster.so/api/v2/public/airflow/events",
        headers={
            "Authorization": f"Bearer {BUSTER_API_KEY}",
            "Content-Type": "application/json"
        },
        json={
            "event_type": "dag_run_failed",
            "dag_id": context['dag'].dag_id,
            "task_id": context['task'].task_id,
            "execution_date": str(context['execution_date']),
            "error_message": str(context.get('exception', 'Unknown error'))
        }
    )

# Add to DAG default_args
default_args = {
    'on_failure_callback': notify_buster_on_failure,
}

name: pipeline_failure_handler

triggers:
  - event: airflow
    type: dag_run_failed
    includes:
      - "critical_pipeline"

prompt: |
  An Airflow DAG has failed. Investigate:
  1. Check the error message from the trigger context
  2. Look for related models in the repository
  3. Create a GitHub issue with investigation steps
  4. Alert #data-incidents on Slack

tools:
  include:
    - slack_tool

triggers:
  - event: monitor
    types: ['schema_drift', 'freshness']
    severity: ['medium', 'high']

name: schema_drift_handler
description: Responds to schema drift alerts

triggers:
  - event: monitor
    types: ['schema_drift']
    severity: ['medium', 'high']

prompt: |
  A schema drift has been detected in the data warehouse.
  
  **Monitor**: {{monitor.name}}
  **Severity**: {{run.severity}}
  **Reason**: {{run.reason}}
  
  **Changes Detected**:
  {{#each details.changes.added}}
  - ADDED: {{this.path}}
  {{/each}}
  {{#each details.changes.deleted}}
  - DELETED: {{this.path}}
  {{/each}}
  
  Analyze these changes and:
  1. Determine if this is expected (deployment, migration) or unexpected
  2. If unexpected, investigate potential impacts on downstream models
  3. Update YAML documentation if needed
  4. Summarize findings and recommend next steps

tools:
  include:
    - slack_tool

name: freshness_handler
description: Investigates stale data alerts

triggers:
  - event: monitor
    types: ['freshness']
    severity: ['high']

prompt: |
  Data freshness alert detected.
  
  **Monitor**: {{monitor.name}}
  **Severity**: {{run.severity}}
  **Reason**: {{run.reason}}
  
  Investigate this freshness issue:
  1. Check when the table was last updated
  2. Look for recent pipeline failures in Airflow
  3. Check source system status
  4. Alert #data-incidents on Slack with findings

tools:
  include:
    - slack_tool

name: documentation_maintainer

triggers:
  # Update docs when PRs change models
  - event: pull_request
    types: ['opened', 'synchronize']
    includes:
      - "models/**/*.sql"
  
  # Weekly comprehensive audit
  - event: scheduled
    cron: "0 9 * * 1"
    branches: ['main']
  
  # Post-merge updates
  - event: push
    branches: ['main']
    includes:
      - "models/**/*.sql"

prompt: |
  Maintain documentation for dbt models.
  
  If triggered by a PR: Update docs for changed models only.
  If triggered by schedule: Audit all models for missing docs.
  If triggered by push: Ensure merged changes have complete docs.

# Good: Only triggers on SQL changes
triggers:
  - event: pull_request
    includes:
      - "models/**/*.sql"

# Avoid: Triggers on every file change
triggers:
  - event: pull_request

# Agent 1: Monday 9 AM
triggers:
  - event: scheduled
    cron: "0 9 * * 1"

# Agent 2: Monday 10 AM (staggered)
triggers:
  - event: scheduled
    cron: "0 10 * * 1"

triggers:
  # Catch issues during review
  - event: pull_request
    types: ['opened', 'synchronize']
    includes: ["models/**"]
  
  # Catch anything that slipped through
  - event: scheduled
    cron: "0 9 * * *"
    branches: ['main']