alex/headquarter
1
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source 
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
This commit is contained in:
Developer
2026-06-15 09:10:05 +00:00
parent f0ae9483f3
commit 6e33e8e4e9
29 changed files with 245 additions and 62 deletions
Download Patch File Download Diff File Expand all files Collapse all files
apps/.pi-map.md
+1 -1
View File
@@ -7,7 +7,7 @@ index: apps/.pi-map.index.md
Contains the main application entry points and executable modules for the project.
## files
## arch
Typically follows a modular or microservices architecture where each subdirectory represents an independent deployable application sharing common libraries or frameworks.
Typically follows a modular architecture where each subdirectory represents a separate deployable application or service, often with shared libraries extracted to common packages.
## tags
-
## symbols