chore(workers): migrate worker config to librefang Cloudflare account#6092
Conversation
houko
left a comment
houko
left a comment
There was a problem hiding this comment.
The other three workers (marketplace-worker, registry-worker, stats-worker) now have account_id hardcoded to the new librefang account in their wrangler.toml files.
visit-counter-worker has no account_id field at all (before or after this PR), so it will fall back to the CLOUDFLARE_ACCOUNT_ID Actions secret — which currently still targets the old account.
This means in the window between merging this PR and rotating the secret, the three explicit-account_id workers deploy to the new account while visit-counter-worker deploys to the old one.
Consider adding:
account_id = "57449de851e4289a4407a73e66baaac9"to web/workers/visit-counter-worker/wrangler.toml (after compatibility_date) so all four workers are consistent and the new target is enforced independently of the secret rotation timing.
Generated by Claude Code
…unt_id (#6093) PR #6092 migrated the worker config to the librefang Cloudflare account, changing `account_id` in `web/workers/marketplace-worker/wrangler.toml` and `web/workers/registry-worker/wrangler.toml` from `3ee9bb52…` to `57449de8…`. detect-secrets flags that value as a Base64 High Entropy String, so its baseline hash changed, but `.secrets.baseline` still carried the old hash and the secret-scan job on main failed against the committed baseline. Update only the two wrangler.toml entries to the rescanned hash (`abfc409c…`). The unrelated `plugin_manager/registry.rs` embedded-pubkey entry that coincidentally shares the old hash is left untouched. Co-authored-by: Evan <[email protected]>
1 participant
What
Point the Cloudflare Worker configs at the new librefang Cloudflare account after the cross-account migration.
account_id-> librefang account (57449de851e4289a4407a73e66baaac9)database_id-> migrated database (1bbf40ca-963b-4b94-b65d-062b9e7bbb42)REGISTRY_PUBLIC_KEY-> rotated Ed25519 signing keyAffects
marketplace-worker,stats-worker,visit-counter-worker,registry-worker.Why
librefang.ai, all workers, D1, and KV have been migrated from the previous Cloudflare account to the dedicated librefang account. The workers are already deployed and serving there; this updates the repo sodeploy-worker.ymltargets the new account too.Follow-up after merge
Repoint the repo Actions secrets, otherwise CI keeps deploying to the old account:
CLOUDFLARE_ACCOUNT_ID->57449de851e4289a4407a73e66baaac9CLOUDFLARE_API_TOKEN-> a token scoped to the librefang account (Workers + Pages)