Repository navigation
Upstream the vendored Cloudflare Pages bootstrap fix - #3
Merged
Merged
Conversation
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
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.
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.