Repository navigation
EdgeZero full migration (umbrella tracker) #840
Description
Description
Umbrella tracker for moving Trusted Server onto EdgeZero primitives across store access, configuration, secrets, route handlers, and eventual removal of the legacy Fastly path. Each phase has its own issue and implementation review; this tracker records dependencies and completion status rather than replacing those issues.
The original design referenced docs/superpowers/specs/2026-07-02-edgezero-full-migration-design.md in PR #839. That file is absent from the current checkout, so use the linked PR and phase issues as historical design context until a maintained spec location is confirmed.
Phases
- Phase 0: upstream EdgeZero
State<T>extractor and nested/array#[secret]support (add State<T> + nested #[secret] design spec edgezero#305); verify the current upstream dependency before treating this as complete. - Phase 1: EdgeZero migration Phase 1 — Stores onto EdgeZero StoreRegistry #841 move stores to EdgeZero
StoreRegistry. - Phase 2: EdgeZero migration Phase 2 — Finish config injection (no embedded toml) #842 finish config injection (closed on GitHub).
- Phase 3: EdgeZero migration Phase 3 — Full secret externalization #843 externalize secrets; depends on Phase 0.
- Phase 4: EdgeZero migration Phase 4 — Handlers to extractors #844 migrate handlers to extractors; depends on Phase 0 and follows store work where practical.
- Phase 5: EdgeZero migration Phase 5 — Delete legacy Fastly path (gated) #845 legacy Fastly path deletion issue is closed; confirm the rollout gate in Fastly entry point switch (dual-path with flag) #495 and actual code state before treating full migration as complete.
Design decisions to preserve or revisit
The original tracker called for load-once Arc<Settings> via State<Settings>, deferred migration of the integration proxy router, startup secret resolution, and collapsing TrustedServerAppConfig into Settings. Reconcile these decisions with the currently pinned EdgeZero version and adapter architecture before changing handler contracts.
Done when
- Each phase issue is closed with implementation evidence or an explicit decision to drop that phase.
- The four supported adapters use the intended EdgeZero contracts and route parity tests pass.
- The maintained migration design and rollout status are linked from this tracker, with any remaining legacy path documented.
Activity