Files

T

Developer 6e33e8e4e9 fix: remove explicit repo mount from pi-agent manifest and derive workspace name from remote URL

The pi-agent manifest still declared an explicit repo mount with
{{WORKSPACE_NAME}}, making the mount target dependent on tool config. The
instance service now synthesizes the repo mount, so the manifest no longer
needs the explicit mount.

- Add Alembic migration 2026_06_15_090500 to remove the source_type: repo
  mount from the built-in pi-agent manifest
- Add _get_repository_mount_name() helper to derive the workspace directory
  name from the repository remote URL (matching git clone behavior) and
  fall back to the user-provided repository name
- Use the helper for WORKSPACE_NAME/REPO_NAME in manifest, legacy dockerfile,
  and legacy compose template paths
- Update unit tests for the new migration and helper

Quality gates:
- pytest tests/unit: 218 passed
- ruff: clean on changed files
- mypy: clean on changed files
- alembic heads: single head

2026-06-15 09:10:05 +00:00

680 B

Raw Blame History

apps/api/alembic (index)

dir: apps/api/alembic

role

Database migration infrastructure for the API application, providing version-controlled schema changes with async SQLAlchemy support.

parent

index: apps/api/.pi-map.index.md map: apps/api/.pi-map.md

children

apps/api/alembic/versions index: apps/api/alembic/versions/.pi-map.index.md map: apps/api/alembic/versions/.pi-map.md

files

env.py
script.py.mako

links

index: apps/api/alembic/.pi-map.index.md map: apps/api/alembic/.pi-map.md

workflows

change alembic behavior read: env.py, script.py.mako
explore alembic subdirectories index: apps/api/alembic/versions/.pi-map.index.md

680 B Raw Blame History