DashboardcraftCraft Cloudflare target: deployType def…

Craft Cloudflare target: deployType defaults to worker, account ID optional

Category: architecture
Confidence: 0.90
ID: 019f8443-d24f-7700-bb77-b32cb1313fcc
Project ID: e16af391-c497-4837-b681-c849a5514499
Cross-project: No
Recalled in other projects: 1
Source session: 034TaUm9363zGEG6E
Created: 2026-07-21 10:29:48
Updated: 2026-07-21 10:41:05

Cross-Project Recalls

ProjectHitsLast recalled
opencode-lore 2 2026-07-27

Content

Cloudflare target's deployType config default flipped from pages to worker (Cloudflare is steering new projects to Workers; Pages is positioned as legacy but still supported via deployType: pages). CLOUDFLARE_ACCOUNT_ID is optional — only CLOUDFLARE_API_TOKEN is required/secret; account ID is a non-secret identifier, forwarded to wrangler only when set, else wrangler auto-discovers it (single-account tokens) or errors listing account IDs in non-interactive/CI multi-account cases. No Cloudflare SDK added — raw global fetch used (Node 24.18.0 baseline). CLOUDFLARE_API_TOKEN always passed via env vars, never CLI argv/logs. Wrangler v4 has no built-in OIDC/keyless auth (unlike craft's npm target OIDC path) — auth is via API token, legacy Global API Key (deprecated), or wrangler login OAuth only. Introduced as a PR #843 follow-up; adversarial review verdict: solid, no CRITICAL/MAJOR issues.

Move to: