phenix-travelprotection-api
Stateless .NET 8 API that calculates the travel protection state (ATOL/package schemes) and associated fees for each component of a booking or quote.
Health score
0 to 100 across seven weighted factors; nothing is hidden. Green is 75 and above, amber 50 to 74, red below 50. How scoring works.
Facts
| Languages | csharp |
| Frameworks | ASP.NET Core 8 |
| Runtimes | .NET 8, .NET Standard 2.0 |
| Tests / CI | good / CI in place |
| Last commit | 2026-07-24 |
| Owner | Owner unknown (mapping to be curated) |
| Domain | Bookings and fulfilment (system generated; curate in repo-owners.json to override) |
| Product area | Phenix |
| Hosted | On-prem Deployed to our own machines
|
| Releases | 2 release pipeline(s): \ops\travelprotection\phenix-travelprotection-api CI; \ops\travelprotection\phenix-travelprotection-api stealth |
| Integration | rest |
| Source | Open in Azure DevOps |
Risk flags
No risk flags recorded.
Each flag links to its glossary definition.
Dependencies in context
Entanglement
loosely attached Bound into the core by 1 mechanism(s).
- Pinning dependency: phenix-feature-service
Detaches when its pinning dependencies are cut or multi-targeted (phenix-feature-service).
Migration playbooks
Generated from this repo's assessment data: what is feasible, what blocks it, and the steps in order. Ratings: green means actionable now, amber means sequence other work first, red means blocked, grey means not applicable.
ZDD adoption
No excuseNothing technical is holding this repo on the three-week release. It either already deploys without downtime (AWS) or is a modern, well-tested service the automated stealth path can carry today. Modern runtime, good tests, no hosted legacy transport: the automated stealth path can carry it today.
- 1 system(s) depend on this repo; during a rolling deploy they will talk to old and new versions at once, so responses must stay compatible
- Feature flags come from phenix-feature-service (WCF-only): flag reads themselves are a legacy dependency to watch
- Adopt the four-stage discipline from the ZDD engineering standard: pre-deployment compatibility, deployment, feature activation behind a flag, post-release cleanup.
- Make every change dual-version safe: backwards-compatible APIs (new major version for breaking wire changes), expand and contract for any schema change, and consumers tolerant of unknown fields.
- Audit serialized data: anything in Redis, queues or shared caches must deserialize cleanly across adjacent versions.
- Wrap behaviour changes in feature flags so code deploys dark and release becomes a business decision, not a deployment event.
- Route deployments through the Workflow Engine's automated drain, deploy, health-check, return cycle (the path proven by the first automated production run in mid-2026).
- Verify with area-scoped regression rather than the whole-platform cycle, and watch error rates after rollout with automated rollback on alert.
SQL Server exit
Not applicableNo SQL Server dependency is recorded for this repo. Nothing to migrate.
Containerisation
Ready to containeriseModern runtime, no hosted legacy transport: this service can follow the estate's proven container path (Dockerfile, shared pipeline template, ECS via Terraform).
- Add a Dockerfile and make the app read all configuration from environment variables and the secrets manager, never from machine-local files.
- Log to stdout and expose a health check endpoint so ECS can supervise it.
- Adopt the shared ci.yml pipeline template with the container parameters (awsRegion, containerAfterBuild, ecsTerraformRepo), which is exactly how the estate's existing AWS services deploy.
- Define the service in the Terraform repo, deploy to a non-production environment, then shift traffic and disarm the deployment-group release pipeline.
Recommended actions
No specific actions for this repo. It either needs only normal maintenance, or its work is covered by an estate-level action. See the full programme.
Assessment notes
phenix-travelprotection-api
Purpose
Calculates what level of travel protection (None, FlightOnly, TC package, external package, etc.) each component of a booking/quote needs, and what fees apply (ATOL, calamity fund, package usage, cruise connection insurance, SGR, TC protection fee). Deliberately stateless — the request carries all the data needed. Also publishes TC.TravelProtection.Contract and multi-targeted TravelProtection.Api.Client NuGet packages for callers.
Tech stack
C# ASP.NET Core on .NET 8 (README still says .NET 6) with API versioning and Swashbuckle. The contract library targets .NET Standard 2.0; the client library multi-targets net462/net481/netstandard2.0 with Autofac and SimpleInjector integration packages for legacy consumers. Uses TC.ConnectionBroker 1.19 (Api + Mongo), TC.Exceptions middleware, WebApi.Logger, TC.Diagnostics health checks.
Deployment
Included as prod_application with 2 releases: \ops\travelprotection\phenix-travelprotection-api CI and ... stealth, from one build pipeline. YAML CI (azure-pipelines.yml plus build-api-client.yml for the client package) using shared InternalOSS/azure-pipelines-templates. Per-environment appsettings (QA, Preproduction, Training, Live).
Dependencies
Internal packages: TC.ConnectionBroker.* (tc-connectionbroker), TC.Exceptions.* (tc-exceptions), TC.Phenix.CompanyInfo (company-info-api), TC.Phenix.Feature (phenix-feature-service), plus WebApi.Logger and TC.Common.Hypermedia (shared packages, source repos not confirmed). No third-party external services — the core calculation is self-contained.
Data stores
MongoDB travelprotection_logs database for request/response logging via WebApi.Logger MongoDB sink (with a Mongo health check). No business data store of its own.
Integration points
Inbound REST only (versioned controllers, Swagger). No message bus, no WCF. Feature flags and company-info config are pulled over REST from the respective Phenix services.
Code health
Strong: one xUnit test project with 34 test files covering the TPS and fee calculators; README claims ~96% branch coverage and reads as genuinely maintained documentation. Actively developed (last commit 2026-07-24). Modern SDK-style projects, YAML CI, version.json/Nerdbank-style versioning.
Modernisation risks
Low. Modern .NET 8 runtime, good tests, YAML pipelines. Business-rule dates hardcoded in appsettings (FlightPlus end date, SGR start date) are configuration debt rather than risk. The net462/net481 client targets exist only to serve legacy consumers and can be dropped as those consumers modernise.