menzeljandClaude Opus 5
51d1998307
StackPilot now manages exactly one Docker host: the one it runs on. The
stackpilot-agent sidecar and everything that proxied to it are gone — 4721
lines deleted against 657 added.
Deleted outright: agent/ (image, compose, env), agent_app.py, models/agent.py,
routers/agents.py (1200 lines), services/agent_service.py, the agent API client,
RemoteStackDetail, the host components and AgentStacksSection. That removes 57
API routes and the three /ws/agent-* proxies.
Threaded out everywhere else, which was the bulk of the work. Every API module
carried an optional agentId that switched the base path; every page that listed
Docker objects rendered one section per host behind a HostHeader; Files had a
host switcher; the New Stack editor and the template dialog had host selectors;
schedules, auto-update policies and stack summaries carried agent_id. All of it
is gone, and the typechecker drove the sweep — 85 files touched, tsc and the
build clean.
Two things the removal exposed as dead weight rather than merely unused:
compose_service kept an in-process busy set purely because the agent needed a
lock and has no database. With the agent gone that was a second source of truth
next to the real DB lock, so it is deleted; compute_status now reports only what
the containers say and the two callers that want "updating" overlay the lock.
StacksTable's linkBase prop only ever existed to point at /hosts/{id}/stacks.
The dashboard's "Hosts 1/1 online" KPI can no longer say anything else, so the
tile and the KPIs behind it are gone and the row is five wide.
Upgrading matters here. An existing install still has an agent table holding
each remote host's URL and bearer token — full Docker control of that host,
sitting in the database with nothing left to use it. _drop_removed_schema drops
it on first start, and drops the agent_id columns where the SQLite build
supports DROP COLUMN. Each statement runs in its own transaction on purpose: a
failed DDL poisons the transaction it is in, so sharing one would let an
unsupported column drop take the table drop down with it. test_agent_removal
covers both branches plus the fresh-install and idempotent cases, and an
end-to-end run against a seeded pre-0.48 database confirms the table is gone and
every /api/agents route answers 404.
Docstrings that justified a design by "shared with the agent, which has no
database" were rewritten rather than left lying: update_service's persistence
callback and image_status_store are still the right split (registry logic stays
testable without a database), but for that reason now, not the old one. The
README's multi-host sections are removed and an upgrade note explains what to do
with running agent containers; ROADMAP keeps its history behind a note saying
the feature it describes no longer exists.
CI no longer builds or pushes stackpilot-agent.
735 tests pass, ruff and tsc clean.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Dk43rmEeRfYi5wsLDbmfyG
74 lines
2.6 KiB
Python
74 lines
2.6 KiB
Python
"""Runtime state that used to live in module-level dicts.
|
|
|
|
Three things were kept in process memory: which stacks are mid-deploy, the
|
|
registry digests behind the "update available" badges, and the login rate
|
|
limiter's counters. All three assumed exactly one uvicorn worker — nothing said
|
|
so, and ``--workers 2`` would have silently given each worker its own copy —
|
|
and all three were lost on restart.
|
|
|
|
They are tables now. SQLite is already here; this needs no new dependency.
|
|
|
|
"""
|
|
from __future__ import annotations
|
|
|
|
from datetime import datetime, timezone
|
|
from typing import Optional
|
|
|
|
from sqlmodel import Field, SQLModel
|
|
|
|
|
|
def _now() -> datetime:
|
|
return datetime.now(timezone.utc)
|
|
|
|
|
|
class StackLock(SQLModel, table=True):
|
|
"""A stack is mid-operation and must not be touched concurrently.
|
|
|
|
``docker compose`` has no locking of its own, so two simultaneous ``update``
|
|
calls — two browser tabs, or auto-update racing a manual click — would both
|
|
run ``pull`` and ``up`` against the same project and fight over recreating
|
|
containers.
|
|
|
|
``expires_at`` is what keeps a crashed worker from locking a stack forever:
|
|
an expired row is simply taken over by the next caller.
|
|
"""
|
|
|
|
stack_id: str = Field(primary_key=True)
|
|
action: str # "update", "start", "backup", …
|
|
#: Free-form owner, for the log when a lock is stolen. Not a security control.
|
|
owner: str = ""
|
|
acquired_at: datetime = Field(default_factory=_now)
|
|
expires_at: datetime
|
|
|
|
|
|
class ImageStatus(SQLModel, table=True):
|
|
"""Cached result of one image's registry digest check.
|
|
|
|
Persisted so a restart does not blank every update badge until the next
|
|
background sweep (up to an hour), and so ``notified`` survives with it —
|
|
otherwise every restart re-announced the same pending updates.
|
|
"""
|
|
|
|
image: str = Field(primary_key=True)
|
|
update_available: bool = False
|
|
current_digest: Optional[str] = None
|
|
remote_digest: Optional[str] = None
|
|
checked_at: float = 0.0
|
|
error: Optional[str] = None
|
|
#: Whether an "update available" notification already went out for this
|
|
#: image at its current state.
|
|
notified: bool = False
|
|
|
|
|
|
class LoginAttempt(SQLModel, table=True):
|
|
"""One login attempt, for the rate limiter.
|
|
|
|
In memory this reset on every restart, so an attacker could clear their own
|
|
budget by getting the process to restart — and with more than one worker the
|
|
limit multiplied by the worker count. Rows are pruned as they age out.
|
|
"""
|
|
|
|
id: Optional[int] = Field(default=None, primary_key=True)
|
|
ip: str = Field(index=True)
|
|
at: datetime = Field(default_factory=_now, index=True)
|