custom-data-fields-api
ASP.NET Core 8 API for configuring, capturing and retrieving custom data fields that Travel Counsellors display on client invoices and integrate into other applications.
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 11, Serilog, Swashbuckle/NSwag, GraphQL.Client 6 |
| Runtimes | .NET 8 |
| Tests / CI | some / CI in place |
| Last commit | 2026-07-02 |
| Owner | Owner unknown (mapping to be curated) |
| Domain | Platform services (system generated; curate in repo-owners.json to override) |
| Product area | Shared platform |
| Hosted | On-prem Deployed to our own machines
|
| Releases | 1 release pipeline(s): \finance\custom-data-fields\tc-custom-data-fields on-prem |
| Integration | rest, graphql, jwt |
| Source | Open in Azure DevOps |
Risk flags
No risk flags recorded.
Each flag links to its glossary definition.
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
Ready with guardrailsClose: the deployment path exists, but specific checks are needed first, typically raising tests, auditing serialized data, or respecting a shared schema with expand and contract. Test coverage is thin; ZDD shifts the safety net onto automation.
- 2 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
- 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.
- 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
custom-data-fields-api
Purpose
Provides CRUD and retrieval endpoints for corporate custom data fields and their per-booking values, letting Travel Counsellors capture client-specific information for invoices. Includes an integration layer that queries the TC Accounts GraphQL API for Phenix booking details (by Phenix booking id or sales-order id), plus a published NSwag client package (TC.CustomDataFields.API.Client). Full docs live on the Azure DevOps wiki.
Tech stack
C# on .NET 8 (ASP.NET Core, nullable + implicit usings). Layered solution: API, Application, Common, DataAccess, AccountsGraphQLIntegration, Client. Uses Asp.Versioning, FluentValidation, Serilog, Swashbuckle, PhenixAuth JWT bearer authentication, TC.ConnectionBroker (Api/HttpClient/Mongo), TC.Exceptions.WebApiClient, TC.Phenix.User.API.Client, TC.Teams.API.Client, TC.Diagnostics health checks, Nerdbank versioning (version.json).
Deployment
Included as a prod application with 2 releases. Build pipeline custom-data-fields-api on-prem; release pipelines \finance\custom-data-fields\custom-data-fields on-prem Stealth and \finance\custom-data-fields\tc-custom-data-fields on-prem. The azure-pipelines.yml uses the shared templates CI stage with containerAfterBuild: true and AWS region eu-west-1, so builds also produce a container/terraform deployment alongside the on-prem releases. Per-environment appsettings (testqa, qa, preproduction, production).
Dependencies
Internal: tc-connectionbroker for brokered Mongo/HTTP connections, phenix-user-api (user client), teams-service (teams client), webapi-exceptions for centralised exception logging, and the Accounts GraphQL API for booking lookups (repo not identifiable in included.json). Consumers integrate via the published API client package.
Data stores
mongodb:CustomDataFields — collections DataFields, DataFieldValues and RequestLogs, accessed through TC.ConnectionBroker.Mongo.
Integration points
REST/JSON API (versioned, Swagger/OpenAPI, generated client) secured with PhenixAuth JWT; outbound GraphQL queries to the Accounts API over a broker-configured HttpClient.
Code health
Three test projects (Api, Application, Common) — reasonable coverage of the application layer. Modern CI via shared templates v1.0. Actively maintained; last commit 2026-07-02.
Modernisation risks
Low: current .NET 8 runtime, contemporary patterns, active development and tests. Main watch items are the split on-prem/AWS deployment story and keeping the many internal TC packages up to date.