Feature flags
Three feature flag mechanisms, one dormant and one WCF-only.
Recommendation
Introduce one modern feature flag service, migrate the 25 consumers of phenix-feature-service to it, retire tc-features, and remove the hardcoded toggle maps as their hosts are modernised.
The family
| Repo | Role | Health | Entanglement | Note |
|---|---|---|---|---|
| tc-features | Retire | 50 · amber | loose | Dormant since 2019 |
| phenix-feature-service | Retire | 31 · red | kernel | WCF-only on .NET Framework 4.7.2, no tests, 25 dependents; replace with a modern feature flag service |
| phenix-flights | Review | 50 · amber | kernel | Hardcoded company-GUID toggle maps inside the app |
| phenix-retail-configuration-service | Review | 49 · red | loosely attached | Hardcoded toggle maps |
| phenix-passenger-configuration-service-host | Review | 40 · red | kernel | Hardcoded toggle maps |
Actions
Retire phenix-feature-service
WCF-only on .NET Framework 4.7.2, no tests, 25 dependents; replace with a modern feature flag service. Part of the Feature flags consolidation: Introduce one modern feature flag service, migrate the 25 consumers of phenix-feature-service to it, retire tc-features, and remove the hardcoded toggle maps as their hosts are modernised.
Impact: A migration never paid for, a pipeline decommissioned and an attack surface removed
proposedRetire tc-features
Dormant since 2019. Part of the Feature flags consolidation: Introduce one modern feature flag service, migrate the 25 consumers of phenix-feature-service to it, retire tc-features, and remove the hardcoded toggle maps as their hosts are modernised.
Impact: A migration never paid for, a pipeline decommissioned and an attack surface removed
proposedReplace phenix-feature-service with a modern feature flag service
WCF-only feature flags with 25 dependents and no tests. Replacing it releases every consumer whose only legacy tie is a flag lookup.
Impact: Highest leverage in the programme: releases consumers without touching them
proposed