fix(migration): exa env var into db

[jessicasingh7]

Description

[Provide a brief description of the changes in this PR]

How Has This Been Tested?

[Describe the tests you ran to verify your changes]

Additional Options

• [Optional] Override Linear Check

---

Summary by cubic

Seeds the Exa internet search provider from the EXA_API_KEY environment variable during migration and encrypts the API key. Activates it only if no provider is active; no-op if the env var is missing or the provider already exists.

• Migration
  • Set EXA_API_KEY before running migrations.
  • Inserts provider named “Exa” with type “exa.”
  • Skips insert if it already exists; safe to rerun.
  • Downgrade is a no-op to preserve existing Exa provider rows.

^{Written for commit 4e29a17. Summary will update automatically on new commits.}

[greptile-apps]

Greptile Overview

Greptile Summary

Adds database migration to seed Exa search provider from EXA_API_KEY environment variable, encrypting the API key and setting provider as active only if no other active provider exists.

Critical Issue:

• Table definition missing required time_created and time_updated timestamp columns that have NOT NULL constraints in the actual schema

Confidence Score: 1/5

• This PR contains a critical bug that will cause the migration to fail at runtime
• The table definition in _get_internet_search_table is missing time_created and time_updated columns that have NOT NULL constraints in the actual schema. This will cause the insert operation to fail because SQLAlchemy won't apply server defaults when using manually-defined Table objects for data manipulation.
• The migration file requires immediate attention to add missing timestamp columns to the table definition

Important Files Changed

File Analysis

Filename	Score	Overview
backend/alembic/versions/3c9a65f1207f_seed_exa_provider_from_env.py	2/5	Adds migration to seed Exa provider from EXA_API_KEY env var, but missing time_created and time_updated columns in table definition

Sequence Diagram

sequenceDiagram
    participant Migration as Migration Script
    participant Env as Environment
    participant DB as Database
    participant Encrypt as Encryption Util

    Migration->>Env: Get EXA_API_KEY
    alt No API key found
        Env-->>Migration: None
        Migration->>Migration: Return early
    else API key exists
        Env-->>Migration: API key value
        Migration->>DB: Get bind connection
        Migration->>DB: Check for existing provider
        alt Provider already exists
            DB-->>Migration: Existing record
            Migration->>Migration: Return early
        else No existing provider
            DB-->>Migration: None
            Migration->>Encrypt: encrypt_string_to_bytes(api_key)
            Encrypt-->>Migration: Encrypted key bytes
            Migration->>DB: Check for active providers
            alt Active provider exists
                DB-->>Migration: Active record found
                Migration->>DB: Insert (is_active=False)
            else No active provider
                DB-->>Migration: No active records
                Migration->>DB: Insert (is_active=True)
            end
            DB-->>Migration: Insert complete
        end
    end

Loading

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

logic: table definition missing time_created and time_updated columns that exist in actual schema (line 33-42 in migration 1f2a3b4c5d6e). These columns have NOT NULL constraints with server defaults. When manually defining sa.Table for data manipulation, include all NOT NULL columns to ensure insert succeeds.

Prompt To Fix With AI

This is a comment left during a code review.
Path: backend/alembic/versions/3c9a65f1207f_seed_exa_provider_from_env.py
Line: 28:38

Comment:
**logic:** table definition missing `time_created` and `time_updated` columns that exist in actual schema (line 33-42 in migration `1f2a3b4c5d6e`). These columns have NOT NULL constraints with server defaults. When manually defining sa.Table for data manipulation, include all NOT NULL columns to ensure insert succeeds.

How can I resolve this? If you propose a fix, please make it concise.

[justin-tahara]

We need to fix this one.

[cubic-dev-ai]

No issues found across 1 file

[justin-tahara]

Make sure to test this and ensure that it works.

[justin-tahara]

We need to fix this one.

[justin-tahara]

Is this how you store the key in the DB?