Repository navigation
feat(tooling): resolve Cloudflare identifiers outside configs - #69
Merged
Merged
Conversation
Let production manifests read the account ID from a named environment variable. Accept a name-only D1 binding after finding exactly one match in the selected account. Apply cf migrations by the observed ID. Co-authored-by: Codex <noreply@openai.com>
WillieCubed
force-pushed
the
codex/id-env
branch
from
September 30, 2026 05:55
57640d1 to
510ad61
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TL;DR
Production setup can read the Cloudflare account from
CLOUDFLARE_ACCOUNT_IDand verify a D1 database by name, allowing lvwwd.org to remove both identifiers from its tracked production config after this tooling release is installed.Overview of Changes
platform.jsonnow accepts either a literalaccountIdor"accountIdEnv": "CLOUDFLARE_ACCOUNT_ID". Production preflight and bootstrap validate the selected account ID before querying resources. Existing manifests keep working.A D1 binding with only a database name is ready only when inventory finds exactly one database with that name in the selected account. An explicit mismatched ID still blocks readiness and migrations. Cf migrations continue to use the observed database ID, including after creation. Unreadable binding config cannot authorize a migration.
Updated the production guide and release notes for 0.6.3.
pnpm checkpassed: 281 CLI tests and 79 web-platform tests.Follow-ups
Publish 0.6.3 through the maintainer's manual release workflow. Then update the lvwwd.org site to consume it, remove the account and D1 IDs from tracked config, and verify production preflight plus the deploy dry run before a live deploy.