tc-actions-api
.NET 10 FastEndpoints API for Travel Counsellor Actions, split out of tc-copilot to let the Actions domain (list/view/outcome feedback) evolve independently.
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 10, FastEndpoints 8 |
| Runtimes | .NET 10 |
| Tests / CI | some / CI in place |
| Last commit | 2026-07-08 |
| Owner | Owner unknown (mapping to be curated) |
| Domain | AI and assistants (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-actions-api
Purpose
Standalone API for Travel Counsellor "Actions", being separated from tc-copilot (phase 1 is API and persistence parity with the existing CoPilot Actions endpoints, no consumer switch-over yet). It lists actions for the authenticated TC with filters, gets single actions, marks actions viewed (fire-and-forget), and updates outcomes singly or in bulk, with ownership rules enforced per Travel Counsellor.
Tech stack
Very modern C#: .NET 10, FastEndpoints 8 with FastEndpoints.Swagger, Phenix.Auth.JWTBearer authentication, slnx solution format, layered API/Services/Data/Models projects. Data layer uses MongoDB.Driver 3.9 via TC.ConnectionBroker.Mongo with TC.ScriptRunner.Mongo migrations; TC health checks are wired in.
Deployment
Included via build->yaml-deploy with 0 classic releases: build pipeline tc-actions-api from the in-repo build.yml using the shared InternalOSS ci.yml template — Linux agents, .NET 10 SDK, containerAfterBuild: true into the phenix container namespace, ECS Terraform from the aws-phenix-tc-apps repo (eu-west-1, functional area phenix).
Dependencies
Internal: TC.ConnectionBroker.* (tc-connectionbroker) for Mongo connection brokering, TC.Diagnostics.HealthChecks (tc-diagnostics-portal). PhenixAuth JWT bearer comes from the shared auth library. No outbound calls to other estate APIs in phase 1.
Data stores
MongoDB TCActions database — reads the Actions collection and writes viewed/outcome events to ActionsFeedback, joining latest feedback on read. This data is the same Actions domain currently served by tc-copilot, so the two services are coupled through the store until switch-over completes.
Integration points
Inbound REST only, versioned under /v1 with OpenAPI via FastEndpoints Swagger and JWT bearer auth scoped to the authenticated Travel Counsellor.
Code health
Actively developed (last commit 2026-07-08) with a genuinely informative README covering purpose, authorization model and data model. Three test projects exist (API/Services/Data) but only ~5 test files so far — coverage is thin for now, consistent with a young service.
Modernisation risks
Low — this is one of the newest stacks in the estate (.NET 10, FastEndpoints, containerised ECS deployment). The watch items are transitional: consumers still point at tc-copilot for Actions, so the shared TCActions Mongo data and duplicate endpoint surface must be retired once switch-over happens, and test coverage should grow with the service.