Skip to content

Upstream the vendored Cloudflare Pages bootstrap fix - #3

Merged
easel merged 1 commit into
mainfrom
codex/upstream-pages-ordering
Oct 30, 2026
Merged

easel merged 1 commit into
mainfrom
codex/upstream-pages-ordering

Conversation

@easel

@easel easel commented Oct 30, 2026

Copy link
Copy Markdown
Contributor

Bring the reusable bootstrap correction from the infrastructure vendored copy back into Concourse. Cloudflare rejects a pages.dev Access destination until its Pages project exists, so new installations now order the empty project before Access, then the custom domain and DNS.

Document the content-pipeline obligation to keep that project empty until admission is verified, and how consumers can vendor the two sibling modules inside a root staged by a read-only plan runner. Infrastructure-specific paths, credentials and caller configuration are not copied into the library.

Validation: all 17 Concourse tests / 148 assertions, strict types/lint/boundaries/build and real Wrangler dry-run; provider validation and mocked foundation plan; a new CI check verifies the actual OpenTofu dependency graph has project -> Access -> domain -> DNS ordering. No state operations, cloud apply or deployment performed.

@easel
easel marked this pull request as ready for review October 30, 2026 20:11
@easel
easel merged commit 3501ec4 into main Oct 30, 2026
4 checks passed
@easel
easel deleted the codex/upstream-pages-ordering branch November 2, 2026 19:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant