Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

void secret sync on Cloudflare prints Synced but stores no secrets, and exits 0 when its prompt is cancelled

未關閉
#635 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
3/5
預估耗時
1-2 天
新手友好度
67/100
Issue 類型
缺陷
描述清晰度
描述清楚
活躍度
活躍
技術堆疊
typescript
領域
cli, cloud

研究方向

Start with the secret.bulk case in packages/void/src/cli/cloudflare-operation-process.ts and trace how bulk secrets are written and how the confirmation prompt handles cancellation. Check the Cloudflare bulk request shape and the existing CLI tests for secret sync. Done means bulk sync stores the secrets, noninteractive confirmation can use --yes, and a cancelled sync exits nonzero.

由索引模型根據 Issue 內容生成。

描述

Filed by Claude Opus 5.5 on behalf of @anaclumos under explicit approval

Two problems with void secret sync on --platform cloudflare. Both were seen on Void 1.3.0 and are still in main's code.

1. The bulk request stores nothing.

void secret sync <file> prints "Synced N secrets" and exits 0. Cloudflare records a new secret-change version for the Worker, but the Worker holds none of the secrets afterwards.

The secret.bulk case in packages/void/src/cli/cloudflare-operation-process.ts writes the bare name-to-secret map as the file it passes to cf workers secrets bulk --file. The Workers secrets-bulk API expects that map wrapped as {"secrets": {...}}.

  • Expected: the secrets are stored, or the command fails with a non-zero exit.
  • Workaround: void secret put NAME with the value on stdin stores one secret, and wrangler secret bulk stores a whole file.

2. Without a terminal it cancels and exits 0.

Without a terminal, as in CI, void secret sync cancels its "This will overwrite N secrets … Continue?" prompt. It then exits 0 without writing anything. No --yes flag exists to confirm without a terminal.

  • Expected: a --yes flag, and a non-zero exit whenever the sync does not run.
主要語言
TypeScript
星號
580
分支
56
平均合併
11 小時 32 分鐘
30 天內合併 PR
158

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

voidzero-dev/void 的其他 Issue

查看 voidzero-dev/void 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。