Skip to content

Integrate Auctioneer into Trusted Server on EdgeZero PR 275 #1505

Open
0 of 6 issues completed
Open

Description

@aram356

Overview

Run Auctioneer's auction engine in-process inside Trusted Server as a local auction provider, on one shared EdgeZero runtime. The approved first host delivery is Fastly banner/display; Auctioneer's broader adapter qualification remains with Auctioneer. This is the Trusted Server side of IABTechLab/auctioneer#8 (Direct Trusted Server Integration). Auctioneer owns the engine and its typed host bridge. Trusted Server owns the host, which means its artifact, runtime services, operator configuration, and auction orchestrator.

Why EdgeZero PR 275 comes first

As reviewed on 2026-11-09, Auctioneer pins EdgeZero to a commit on IABTechLab/edgezero#275 (598f0a2a), while Trusted Server main (4d55a3c6d) still pins v0.0.11. An in-process embed links both into one binary, so both must build against one EdgeZero revision. Auctioneer's bidder calls and Trusted Server's own outbound calls then share one transport, one deadline model, and one set of limits.

The EdgeZero capabilities Trusted Server needs from PR 275 are listed in the requirements document. That is the historical requirements handoff; use the current cutover design in #1506 for the migration. PR 275 remains open and its qualification is incomplete. The maintainer decisions recorded in #1506 on 2026-11-08 make the cutover follow PR 275's head, with main pinning the head the cut was last rebased onto. The cutover merge and production deploys do not wait for the EZ-Q1 record; qualification remains separately tracked in #1508. This changes the scheduling gate, not the evidence required to claim qualification.

Scope

Related

Done when

Affected area

Core, Integrations, Fastly runtime

Milestone review (2026-11-09)

P1. Retain in 202611 as the host-integration coordination issue. Trusted Server's current dependency manifest has not made the SDK cutover or linked Auctioneer. The approved host contract removes a planning gap; bridge, local execution, and artifact acceptance remain delivery work. Keep the remaining work decomposed into #1507–#1512 and follow #1506's recorded maintainer decisions.

Activity

  1. self-assigned this
    on Nov 6, 2026
  2. added theissue type on Nov 6, 2026
  3. added this to the 202611 milestone on Nov 6, 2026
  4. aram356 commented on Nov 13, 2026

    @aram356
    CollaboratorAuthor

    CREATOR: #1507 moved from this epic to #1558, server-side identity on every adapter, because it is that program's first gate: it blocks #1573, #1585, #1586 and #1600, which the MVP waits on, and #1192 and #1556. #1513 and the Auctioneer issues stay here, and #1506 still closes #1507.

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions