tc-profiles-api
Small .NET 8 REST API storing personal profile records for Travel Counsellors — emergency contacts and expression-of-wishes details — in a TcProfiles MongoDB database.
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, FluentValidation, Mapster |
| Runtimes | .NET 8 |
| Tests / CI | some / CI in place |
| Last commit | 2025-10-24 |
| Owner | Owner unknown (mapping to be curated) |
| Domain | Identity and access (system generated; curate in repo-owners.json to override) |
| Product area | Shared platform |
| Hosted | AWS Deployed to AWS
|
| Releases | 0 release pipeline(s): |
| Integration | rest, jwt |
| Source | Open in Azure DevOps |
Dependencies in context
Entanglement
loose No binding mechanisms apply: this system needs no untangling work.
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. Already deploys as a container to AWS, which releases without downtime today. Separating it from the three-week release is a process decision, not a technical one.
- Adopt the four-stage discipline from the ZDD engineering standard: pre-deployment compatibility, deployment, feature activation behind a flag, post-release cleanup.
- Raise automated test coverage first: ZDD trades the end-of-sprint manual gate for continuous automated confidence, so the tests are the entry ticket.
- 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.
- Use ECS rolling deployments with health checks gating traffic, and take this service off the three-week release train.
- 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
Already containerisedIts pipelines already build containers and deploy to AWS. Nothing to do here.
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
tc-profiles-api
Purpose
Holds sensitive personal profile data for agents: an EmergencyContactsController and an ExpressionOfWishesController (next-of-kin/wishes information), with a JwtUserAccessor resolving the calling user from their JWT and an AccessManager gating who may read or edit a profile. Records persist to MongoDB. One of the smallest services in the estate — four source projects and two controllers.
Tech stack
Modern C# on .NET 8 (Api, core, Abstractions, Persistence projects): FluentResults, FluentValidation, Mapster, Scrutor, Swashbuckle, System.IdentityModel.Tokens.Jwt for claims access, MongoDB.Driver via TC.ConnectionBroker.Mongo, TC.ScriptRunner.Mongo migrations, TC.Diagnostics.HealthChecks.
Deployment
No classic release pipelines (release_count 0); single build pipeline tc-profiles-api from azure-pipeline.yaml using the shared InternalOSS/azure-pipelines-templates ci.yml (SDK 8.x), building the API container in namespace phenix and deploying to ECS via Terraform tfvars in aws-phenix-tc-apps, functional area phenix. Only base and Development appsettings are in-repo — environment config comes from the deployment side.
Dependencies
Internal packages: TC.ConnectionBroker.* (tc-connectionbroker), TC.Diagnostics.HealthChecks (tc-diagnostics-portal). No calls to other estate APIs and no external third-party services.
Data stores
Owns the TcProfiles MongoDB database (ConnectionBroker target TcProfiles; emergency-contact and expression-of-wishes collections, script-runner migrations).
Integration points
Inbound REST only (Swagger, JWT-derived user identity with per-profile access checks). No message bus, WCF or outbound HTTP.
Code health
Adequate for its size: two xUnit test projects with 91 facts/theories covering API and manager layers (NSubstitute/FluentAssertions, coverlet). README is untouched boilerplate. Last commit 2025-10-24 — quiet for around nine months, plausibly feature-complete.
Modernisation risks
Low. Clean, modern .NET 8 service with YAML CI and tests. The main considerations are data-protection rather than technical: it stores sensitive personal data (emergency contacts, expression of wishes) so retention/access policies matter more than the stack, and the boilerplate README documents none of that.