Skip to content

Integration-branch revision with the Cloudflare parts #492

Open

Description

@aram356

Summary

Integration-branch revision with the Cloudflare parts.

Behavior

EdgeZero keeps the integration branch rc/identity for this work (DEC-5, #495). Each integration point is a commit on it that Trusted Server main pins by SHA until EdgeZero releases the work; there are no tags. The branch moves only forward, by merges, and is never force-pushed. R1 is the first commit that carries #275 through #439, so Axum production serving does not wait for the record contract. R1b adds EZI-2a and EZI-2b. R2 adds the Fastly and Axum parts of EZI-1. R2b adds EZI-3, #90, #92, the JA4 accessor (#283) and Axum's geo binding (EZI-4a), so providers never wait on JA4. Together R1, R1b, R2 and R2b cover Fastly and Axum. R3 adds the Cloudflare parts of EZI-1 to EZI-4, and R4 the Spin parts. EZI-2p and EZI-5 follow the MVP (DEC-15).

Acceptance criteria

  • Each integration point is a commit on rc/identity that Trusted Server main pins
  • R1, R1b, R2 and R2b contain no Cloudflare or Spin part

Dependencies

Blocked by:

Waits on these decisions:

  • DEC-8 Cloudflare and Spin store (open). Which store Cloudflare and Spin use by default for the record: the DynamoDB or celld adapter, or a native store that meets the contract, per Platform support. Blocks EZI-2c, EZI-2s, R3, T8 and T9.

Blocks:

Related

Activity

  1. added theissue type on Nov 13, 2026
  2. changed the title [-]Integration-branch tag with the Cloudflare parts[/-] [+]Integration-branch revision with the Cloudflare parts[/+] on Nov 15, 2026
  3. ChristianPavilonis commented on Nov 18, 2026

    @ChristianPavilonis
    Collaborator

    @prk-Jr #517 is ready for review and closes #91, so Cloudflare ClientInfo will stop blocking this once it merges. It builds on #514. Cloudflare reads CF-Connecting-IP and the cf TLS fields only when the manifest sets [adapters.cloudflare.client_info] direct_ingress = true.

    Still open here after that: #480 (#514), #478 (#512), and #479, which has no assignee or PR yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions