4 Commits

Include renames

Author	SHA1	Message	Date
jpmschweitzerandClaude	933196c2a2	feat(executors): back up Portainer's own state ... Portainer keeps every stack definition, endpoint, user and access-control rule in a BoltDB inside the portainer_data Docker volume. That volume sits under /var/lib/docker/volumes/, and the daily config backup covers ~/docker-data and code-server-config only — so the thing that defines all 24 stacks was the one thing not backed up. Calls Portainer's /api/backup rather than tarring the volume. BoltDB is a single memory-mapped file, so copying it while Portainer writes can capture a torn page; the API serialises a consistent snapshot. A 200 whose body is not a readable archive is treated as failure. An archive that will not open is worse than a missing one, because it looks like a backup until the day it is needed. Writing that check found a real gap in it: a truncated tar.gz raises EOFError, which is neither TarError nor OSError, so the first version of the guard let it through. Archives contain TLS certificates and private keys and are written 0600. Retention only ever deletes files matching the exact name this executor writes, so an unrelated archive left in the same directory survives. Co-Authored-By: Claude <noreply@anthropic.com>	2026-08-08 19:56:44 +02:00
jpmschweitzerandClaude	7b80e30691	feat(executors): add docker prune executor ... Non-interactive equivalent of system-admin-toj's prune-docker.sh, which prompts per stage and so cannot run from cron. Only the stages that discard regenerable data run by default: build cache and dangling images. Unused images and volumes are opt-in, because docker volume prune removes volumes belonging to merely-stopped containers rather than only orphaned ones, which on this host is a plausible way to lose a database. A failing stage is reported and the remaining stages still run, since a partial reclaim beats none, but the task still ends up failed so the error is not swallowed. Co-Authored-By: Claude <noreply@anthropic.com>	2026-08-08 11:00:42 +02:00
jpmschweitzerandClaude	788c03514a	feat(executors): add postgres retention executor ... Deletes rows past a retention window from a table on the shared Postgres server. Written for sysmon's check_history, which grows with every monitoring check and had no retention at all despite the docs promising a 30-day rolling window. Connects with the Scheduler's own credentials and overrides only the database name, so no second set of secrets enters the stack. The target database grants scheduler_user just SELECT and DELETE on the table, so a bug here can drop old rows but cannot corrupt or forge history. Table and column names cannot be bound as query parameters, so both are validated against a strict identifier pattern before interpolation, and a retention window below 1 day is refused rather than silently emptying the table. Co-Authored-By: Claude <noreply@anthropic.com>	2026-08-08 11:00:42 +02:00
jpmschweitzerandClaude Opus 4.5	64574bcc39	Initial commit: scheduler service extraction from portainer-core ... Extracted standalone scheduler service with: - FastAPI REST API for task management - APScheduler-based task execution - PostgreSQL persistence - Docker container support - Gitea Actions CI/CD workflow 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>	2025-12-11 11:59:32 +01:00