Title: platform: interrupted install ignores a replacement runtime token and never updates deployed Workers · Issue #666 · voidzero-dev/void · GitHub
Open Graph Title: platform: interrupted install ignores a replacement runtime token and never updates deployed Workers · Issue #666 · voidzero-dev/void
X Title: platform: interrupted install ignores a replacement runtime token and never updates deployed Workers · Issue #666 · voidzero-dev/void
Description: Summary Suppose void platform install stops after it has created resources or deployed the API and proxy Workers, and the operator then has to replace the runtime token, for example because the original was revoked or rotated. Resuming w...
Open Graph Description: Summary Suppose void platform install stops after it has created resources or deployed the API and proxy Workers, and the operator then has to replace the runtime token, for example because the ori...
X Description: Summary Suppose void platform install stops after it has created resources or deployed the API and proxy Workers, and the operator then has to replace the runtime token, for example because the ori...
Opengraph URL: https://github.com/voidzero-dev/void/issues/666
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"platform: interrupted install ignores a replacement runtime token and never updates deployed Workers","articleBody":"### Summary\n\nSuppose `void platform install` stops after it has created resources or deployed the API and proxy Workers, and the operator then has to replace the runtime token, for example because the original was revoked or rotated. Resuming with `VOID_PLATFORM_RUNTIME_CLOUDFLARE_API_TOKEN=\u003creplacement> void platform install --resume --name \u003cid>` has two problems:\n\n1. The CLI keeps using the runtime token saved in the checkpoint and ignores the replacement in the environment.\n2. Even when the replacement is used, Workers that are already deployed keep their old `CF_API_TOKEN` secret.\n\n### Where this happens (v1.5.0)\n\n**The saved token wins once the install is past the draft stage.**\n\n- A resumed install counts as a \"setup draft\" only while it has no resources and no API URL: https://github.com/voidzero-dev/void/blob/afeeff6a4d72682f6cfb6c947e9a2c29393c00a6/packages/void/src/cli/platform-setup-draft.ts#L32-L40\n- For any later stage, `configured()` prefers the checkpoint value over the environment variable: https://github.com/voidzero-dev/void/blob/afeeff6a4d72682f6cfb6c947e9a2c29393c00a6/packages/void/src/cli/platform-lifecycle.ts#L915 and https://github.com/voidzero-dev/void/blob/afeeff6a4d72682f6cfb6c947e9a2c29393c00a6/packages/void/src/cli/platform-lifecycle.ts#L936-L939\n- The recovery for a rejected token (clear the saved token, then prompt for a replacement) only runs for a draft on a TTY: https://github.com/voidzero-dev/void/blob/afeeff6a4d72682f6cfb6c947e9a2c29393c00a6/packages/void/src/cli/platform-lifecycle.ts#L969-L1043\n\n So a non-draft resume with a revoked saved token fails verification every time, and an environment replacement does not help.\n\n**Existing Workers never receive the new token.**\n\n- The install path builds its secrets without `updateExistingWorkers`, so `workerSecretUpdates` is empty: https://github.com/voidzero-dev/void/blob/afeeff6a4d72682f6cfb6c947e9a2c29393c00a6/packages/void/src/cli/platform-lifecycle.ts#L1154-L1169 and https://github.com/voidzero-dev/void/blob/afeeff6a4d72682f6cfb6c947e9a2c29393c00a6/packages/void/src/cli/platform-installer-secrets.ts#L193-L196\n- A Worker whose plan action is not `create` counts as existing: https://github.com/voidzero-dev/void/blob/afeeff6a4d72682f6cfb6c947e9a2c29393c00a6/packages/void/src/cli/platform-install-workers.ts#L274-L281\n- An existing Worker only receives secrets listed in `workerSecretUpdates`: https://github.com/voidzero-dev/void/blob/afeeff6a4d72682f6cfb6c947e9a2c29393c00a6/packages/void/src/cli/platform-installer-secrets.ts#L518-L553\n- Everything else is uploaded as `inherit` from the active version: https://github.com/voidzero-dev/void/blob/afeeff6a4d72682f6cfb6c947e9a2c29393c00a6/packages/void/src/cli/cf-version-api.ts#L137-L142\n\nSo if the old token still verifies, the API and proxy Workers already deployed in the interrupted run keep running with it. Revoking it later breaks app deploys from the platform. Today, only the installed-platform maintenance path passes `updateExistingWorkers: true`: https://github.com/voidzero-dev/void/blob/afeeff6a4d72682f6cfb6c947e9a2c29393c00a6/packages/void/src/cli/platform-management.ts#L575-L585\n\n#569 made interrupted credential updates resumable on that maintenance path. The install-resume path does not appear to feed a replacement runtime token into the same mechanism.\n\n### Synthetic repro\n\n1. Run `void platform install --workers-dev` and interrupt it after the API and proxy Workers are deployed but before it finishes, for example by stopping at a later failing step.\n2. Revoke the runtime token in Cloudflare and create a replacement with the same permissions.\n3. Run `VOID_PLATFORM_RUNTIME_CLOUDFLARE_API_TOKEN=\u003creplacement> void platform install --resume --name \u003cid>`.\n4. Runtime token verification uses the saved (revoked) token and fails.\n5. Variant: if step 2 does not revoke the old token, the resume completes, but the API and proxy Workers still hold the old token.\n\n### Questions\n\n1. On a non-draft resume, should an explicit `VOID_PLATFORM_RUNTIME_CLOUDFLARE_API_TOKEN` win over the saved checkpoint value, as it already does for drafts?\n2. When the resolved runtime token differs from the saved one, should resume push `CF_API_TOKEN` to the existing API and proxy Workers through the existing `workerSecretUpdates` and intent mechanism? Or would you prefer that resume refuses and points to a separate command?\n\nI'm happy to open a PR for whichever behaviour you prefer.\n\n_Prepared with Claude Code on behalf of @iPLAYCAFE-dev; reviewed by the maintainer of this account._\n","author":{"url":"https://github.com/iPLAYCAFE-dev","@type":"Person","name":"iPLAYCAFE-dev"},"datePublished":"2026-11-02T09:16:27Z","url":"https://github.com/voidzero-dev/void/issues/666"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react-reconciler,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@d5750093facf |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:b2d51327-bcd8-a6f1-f427-c516bb1dbc4d |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | 8B90:29D44:3B160F:5108CB:6AFB98BD |
| html-safe-nonce | 13df50a144e87adee9a38b470151e58da405575661890f5fa1b6b180e2e5f9d3 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI4QjkwOjI5RDQ0OjNCMTYwRjo1MTA4Q0I6NkFGQjk4QkQiLCJ2aXNpdG9yX2lkIjoiMjMwNjk4NTk4NzcwNTM3OTAwNSIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 8cdf28fd986eed901a0fd4eeea04a6e060c88dfd3a39eb279290d90e8d3e0f9f |
| hovercard-subject-tag | issue:6159630635 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/voidzero-dev/void/666/issue_layout |
| twitter:image | https://opengraph.githubassets.com/75ac69a3a0d64579eb0121d15cb698c9cefd5223428e8b8a6d483a2973333ef1/voidzero-dev/void/issues/666 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/75ac69a3a0d64579eb0121d15cb698c9cefd5223428e8b8a6d483a2973333ef1/voidzero-dev/void/issues/666 |
| og:image:alt | Summary Suppose void platform install stops after it has created resources or deployed the API and proxy Workers, and the operator then has to replace the runtime token, for example because the ori... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | iPLAYCAFE-dev |
| hostname | github.com |
| expected-hostname | github.com |
| None | 4f01efe06174a5ba6342fd58e42d02295e0675bedbb465d6bef2dbaec8e46556 |
| turbo-cache-control | no-preview |
| go-import | github.com/voidzero-dev/void git https://github.com/voidzero-dev/void.git |
| octolytics-dimension-user_id | 149750581 |
| octolytics-dimension-user_login | voidzero-dev |
| octolytics-dimension-repository_id | 1164437080 |
| octolytics-dimension-repository_nwo | voidzero-dev/void |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 1164437080 |
| octolytics-dimension-repository_network_root_nwo | voidzero-dev/void |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | a52db8866b6543b4e83730cd6a6b1360f1a9e4dc |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width