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

Upgrade guide: the current release's snapshot must exist in the new name and format

未关闭 适合新手
#211 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
1/5
预计耗时
1 小时以内
新手友好度
80/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
活跃
技术栈
docker, go, shell

调研方向

该 issue 指向位于 guides/upgrade-to-onebox-names 的升级指南。阅读该指南以理解步骤 5 及其上下文。修复涉及添加一个步骤,将转换后的 ob.yml(v1alpha1 格式)复制到发布目录中,命名为 onebox.snapshot.yml。通过检查发布提交中 ob.yml 的 git diff 来验证更改。编辑指南后,运行任何文档测试或在本地预览更改。

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

描述

bug

Problem

After following guides/upgrade-to-onebox-names, the first ob deploy refuses during planning:

read live secret generation: deploy planning refused: release <current> snapshot unavailable (exit 1):
cat: /var/lib/onebox/app/releases/<current>/onebox.snapshot.yml: No such file or directory

Deploy planning reads the current release's snapshot to find which workloads carry secrets. The release was written by an earlier version as ob.snapshot.yml, in the onebox.run/v1 format this version cannot read, and the guide's step 5 moves the directory but leaves the snapshot as it was.

Found migrating the goal production host. ob bootstrap passed; only the deploy stopped, with the application down.

Workaround used

Copy the project's converted v1alpha1 ob.yml into the current release as onebox.snapshot.yml, keeping ob.snapshot.yml. This is correct only when the converted file describes that release: confirm with git diff <release commit> -- ob.yml that nothing but comments differs.

Fix

Add that step to the guide after step 5, before ob bootstrap, and say that the project file must be converted to v1alpha1 before the host is moved.

主要语言
Go
星标
3
派生
0
平均合并
2 小时 44 分钟
30 天内合并 PR
49

贡献指南

打开贡献指南

从这里开始

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

labstack/onebox 的其他 Issue

查看 labstack/onebox 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

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