databricks.yml

bundle:
  name: youtube-gemini-video-analysis

variables:
  prefix:
    description: "Unique prefix for resource names (e.g., your initials or team name)"
    default: "sc"

targets:
  # No workspace host here on purpose. Pick the target workspace from the CLI:
  #   databricks bundle deploy -t dev  -p <profile>   (or set DATABRICKS_HOST)
  #   databricks bundle deploy -t prod -p <profile>
  # Each target gets its own app and its own Lakebase project, because the
  # resource names below include ${bundle.target}: sc-video-intel-dev vs
  # sc-video-intel-prod. Point dev and prod at different profiles/workspaces
  # (or the same one) as you like.
  dev:
    default: true
    mode: development

  prod:
    mode: production

resources:
  apps:
    video_intelligence_app:
      name: "${var.prefix}-video-intel-${bundle.target}"
      description: "Real-time YouTube video analysis with Gemini + Lakebase history"
      source_code_path: ./app
      resources:
        - name: lakebase-history
          description: "Lakebase database for analysis history"
          postgres:
            branch: "projects/${var.prefix}-video-intel-${bundle.target}/branches/production"
            # The default database name is always "databricks-postgres" (a fixed
            # name, not an auto-generated ID), so this value is deterministic and
            # needs no manual update after deploy.
            database: "projects/${var.prefix}-video-intel-${bundle.target}/branches/production/databases/databricks-postgres"
            permission: "CAN_CONNECT_AND_CREATE"

  postgres_projects:
    video_intel_db:
      project_id: "${var.prefix}-video-intel-${bundle.target}"
      display_name: "Video Intelligence History (${bundle.target})"
      pg_version: "17"