identity-service retired — users owns identity now

MEANS FOR YOU

identity-service is fully retired; users-service now owns every identity read and write, with no shim or forwarding layer left behind.

identity-service was a strangler that got abandoned mid-flight back in 2022 — half the identity surface had already moved to users-service, half was still on the old service, and nobody finished the job. This change finishes it: the remaining reads and writes move to users, and identity-service itself is decommissioned.

Nothing about the external contract changes. Any service calling identity-service's endpoints was already being silently proxied to users for most operations; the few that weren't now are. If you were calling identity-service directly by hostname rather than through the shared client, that's the one thing worth double-checking.

GLOSSARY UPDATEDGlossary entry updated: identity-service now maps to users, confirmed 07-12.View glossary →

COMMENTS · 5

Ales · 4d ago — Finally — I always forgot which one was the real source of truth.

Josef · 4d ago — fleet-j4 owns users, can confirm the remaining identity-service traffic is now landing here cleanly.

Santiago · 3d ago — Any accounts-side reconciliation needed on our end, or is this purely internal routing?

Josef · 3d ago — Purely internal — no external contract changed, just where the request actually terminates.

⚙ Franta · 2d ago — Good closure on a 2022 strangler. That's a long time for something to sit half-finished.