Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Phase 3: Config revisions with rollback for ADF

未关闭
#640 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
30/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
rust
领域
backend, cli

调研方向

Start with the terraphim_orchestrator config handling and the ADF CLI bin crate, using orchestrator.toml and the requested config_history directory as the entry points. Review the referenced Paperclip files for revision patterns. Done means snapshots, listing, rollback, diff, pruning, and the running-agent safety rule all satisfy the acceptance criteria.

由索引模型根据 Issue 内容生成。

描述

enhancement

Parent Epic

#637

Summary

Version the orchestrator TOML config before each change, with CLI rollback capability.

Changes Required

terraphim_orchestrator
  • New config_history/ directory alongside orchestrator.toml
  • Before applying any config change, snapshot current TOML to config-history/YYYY-MM-DDTHH:MM:SS.toml
  • Keep last N snapshots (configurable, default 10)
  • Prune older snapshots on each save
ADF CLI (bin crate)
  • adf config history -- list available snapshots with timestamps
  • adf config rollback <timestamp> -- restore config from snapshot
  • adf config diff <timestamp> -- show diff between current and snapshot
  • Safety: refuse rollback if agents are actively running (or add --force flag)
Config
[config_history]
max_snapshots = 10
history_dir = "/opt/ai-dark-factory/config-history"

Reference

  • Paperclip config revisions: packages/db/src/schema/agent_config_revisions.ts
  • Paperclip agent service: server/src/services/agents.ts (buildConfigSnapshot, config revision tracking)

Acceptance Criteria

  • Config snapshots saved before each change
  • adf config history lists available snapshots
  • adf config rollback restores from snapshot
  • Old snapshots pruned automatically
  • Rollback blocked when agents running (unless --force)
主要语言
Rust
星标
65
派生
5
平均合并
1 小时 17 分钟
30 天内合并 PR
2

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

terraphim/terraphim-ai 的其他 Issue

查看 terraphim/terraphim-ai 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。