Skip to content

fix: persist uv runtimes and mise cache across host replacement - #53

Open
armandocanals wants to merge 1 commit into
mainfrom
codex/persist-uv-mise
Open

armandocanals wants to merge 1 commit into
mainfrom
codex/persist-uv-mise

Conversation

@armandocanals

Copy link
Copy Markdown

Retained worktrees can keep their virtualenvs after a task or host replacement while losing the uv-managed Python installations those virtualenvs reference. This preserves uv's interpreters and package cache on the existing retained EBS volume, and routes mise's cache into its writable persistent data mount.

  • Add narrow mounts for UV_PYTHON_INSTALL_DIR and UV_CACHE_DIR, with host directories prepared and owned before ECS registration.
  • Set MISE_CACHE_DIR inside the existing mise data mount.
  • Document existing-host directory preparation, interpreter migration, verification, and rollback limitations in the generated setup/manage workflows and README. Launch-template updates do not rerun UserData on existing instances, and mounting empty directories does not migrate the old task's files.

No image, compute, EBS capacity, IAM, or networking changes. This branch is based on main and is independent of the Linear integration PR.

Validation:

  • 18 tests pass, including a regression test that parses a renamed generated CloudFormation template and checks writable persistence paths, EBS retention, narrow mounts, bootstrap ordering, and shell syntax. The new test failed before the template change.
  • Lint, format check, CloudFormation lint, docs build, and diff whitespace checks pass.
  • The local generated prototype matches the proposed shipped template, including skills.

Draft pending maintainer live integration-cycle acceptance. The configured integration project and corkboard are unavailable in this checkout; no AWS deployment was performed. Verify existing-host migration and a retained worktree's interpreter after host replacement before accepting. System interpreters and paths outside retained storage are outside this change's persistence guarantee.

@armandocanals
armandocanals marked this pull request as ready for review November 2, 2026 03:20

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant