Files
DocsGPT/docsgpt/alembic/versions/0026_stack_logs_agent_id.py
Alex 574f96341e refactor: rename the application package to docsgpt
The backend import package is now docsgpt, the name it will carry on PyPI;
application was far too generic to install into anyone's site-packages.
git mv plus a mechanical rewrite of every import, dotted string and path
reference: 734 Python files, the compose files, Dockerfile, workflows, docs,
setup scripts, devcontainer, k8s manifests, vscode config, pytest and coverage
config, .gitignore. Behaviour is unchanged.

Kept for one release:
- A top-level application package whose meta-path finder resolves
  application.x.y to the already-imported docsgpt.x.y object, so old imports
  and entry points (celery -A application.app.celery,
  uvicorn application.asgi:asgi_app) keep working with a FutureWarning.
- Celery registers every application.* task name as an alias of its
  docsgpt.* task on start-up, so messages queued by the previous release still
  run. The redbeat key prefix moves to redbeat:docsgpt:v2: so schedule entries
  the previous release wrote are left unread instead of firing twice.

The backend image builds from the repository root (docker build -f
docsgpt/Dockerfile .) so it can ship the alias package; a root .dockerignore
allow-lists docsgpt/ and application/ and keeps caches, local data, .env
files, the sample index files and the Dockerfile out. Compose and the image
workflows point at the new context.
2026-09-07 10:20:43 +01:00

53 lines
1.8 KiB
Python

"""0026 stack_logs.agent_id — stable per-agent attribution for activity logs.
``stack_logs`` (webhook + system-error activity logs) previously carried only
the agent's ``api_key`` string, so it could be joined to an agent only through
that key. Now that agents can rotate their key, a key-only join would orphan
history on rotation. This adds a nullable ``agent_id`` UUID (no FK, mirroring
``token_usage.agent_id`` so a stray/legacy id can never block a log write),
indexes it, and backfills existing rows by matching the stored ``api_key`` to
``agents.key``. The backfill is exhaustive today because no key has been
rotated yet. Idempotent both ways.
Revision ID: 0026_stack_logs_agent_id
Revises: 0025_artifacts
"""
from typing import Sequence, Union
from alembic import op
revision: str = "0026_stack_logs_agent_id"
down_revision: Union[str, None] = "0025_artifacts"
branch_labels: Union[str, Sequence[str], None] = None
depends_on: Union[str, Sequence[str], None] = None
def upgrade() -> None:
op.execute("ALTER TABLE stack_logs ADD COLUMN IF NOT EXISTS agent_id uuid;")
op.execute(
"""
CREATE INDEX IF NOT EXISTS ix_stack_logs_agent_id
ON stack_logs (agent_id)
WHERE agent_id IS NOT NULL;
"""
)
# Backfill from the still-current key mapping. ``agents.key`` is CITEXT and
# unique, so each api_key resolves to at most one agent.
op.execute(
"""
UPDATE stack_logs s
SET agent_id = a.id
FROM agents a
WHERE s.agent_id IS NULL
AND s.api_key IS NOT NULL
AND a.key = s.api_key;
"""
)
def downgrade() -> None:
op.execute("DROP INDEX IF EXISTS ix_stack_logs_agent_id;")
op.execute("ALTER TABLE stack_logs DROP COLUMN IF EXISTS agent_id;")