tc-passport-expiration-service
.NET 8 Quartz-scheduled worker that finds passports expiring within 270 days via the contact API and publishes PassportExpiringSoonEvent messages to Amazon SQS for downstream notification.
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 | Quartz 3, MassTransit 8, Mapster 7, Generic Host |
| Runtimes | .NET 8 |
| Tests / CI | some / CI in place |
| Last commit | 2025-10-23 |
| Owner | Owner unknown (mapping to be curated) |
| Domain | Customer communications (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): \cx\tc-passport-expiration-service |
| Integration | rest, wcf, masstransit, sqs |
| Source | Open in Azure DevOps |
Dependencies in context
Entanglement
loosely attached Bound into the core by 1 mechanism(s).
- Speaks WCF (client)
Detaches when its WCF surface gains a modern interface or its WCF calls move to one.
Depends on / used by
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.
- 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
- Consumes WCF contract packages: never take a breaking client bump mid-feature, and treat obsolete warnings as migration debt
- Serialized state or messages in flight (Redis or queues): new code must deserialize objects written by the previous version
- 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.
- 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
tc-passport-expiration-service
Purpose
A single-job worker: a Quartz cron job (daily at 01:00) calls the contact API for passports expiring 270 days out, enriches each customer with their last booking date via the Phenix booking WCF service, maps the results with Mapster, and batch-publishes PassportExpiringSoonEvent messages onto Amazon SQS via MassTransit. The TC.PassportExpiration.Service.Events contracts project is published as a NuGet package for consumers.
Tech stack
C# on .NET 8 Generic Host (headless). Quartz.NET scheduling, MassTransit 8 over AmazonSQS with TC endpoint-name conventions, Mapster mapping, FluentResults + Polly in the contact API client, TC.ConnectionBroker (Api/Aws/Wcf) for endpoint and credential resolution, Nerdbank GitVersioning, shared StyleCop-style rulesets. Dockerfile plus docker-compose for local runs.
Deployment
Included as prod_application with 1 release: release pipeline \cx\tc-passport-expiration-service from build tc-passport-expiration-service. YAML CI via the shared templates (SDK 8.x) packs the Events package and builds the app, followed by a Docker stage producing the aws-passport-expiration-service image on Linux agents.
Dependencies
Internal: TC.ConnectionBroker.* (tc-connectionbroker); brokered ContactApi HTTP client (phenix-contact-api) for expiring-passport queries; TC.Phenix.Services.Client booking WCF service for last-booking-date lookups (Phenix WCF estate, source repo not confirmed); TC.MassTransit.AmazonSQS conventions. External: Amazon SQS (eu-west-1) with a dedicated CX_PassportExpirationServiceMasstransitUser IAM user.
Data stores
None — all data is read from the contact API and booking service and emitted as events.
Integration points
Outbound REST to the contact API, outbound WCF to the Phenix booking service, and MassTransit publishing over Amazon SQS. No inbound surface.
Code health
One xunit test project with 5 tests covering the core GetExpiringPassportsJob using NSubstitute fakes — proportionate for the tiny codebase but thin. README is untouched boilerplate. Last commit 2025-10-23; the service is feature-complete rather than dormant.
Modernisation risks
Low — modern .NET 8, containerised, YAML CI, own IAM credentials. The main legacy tie is the WCF call into the Phenix booking service via TC.Phenix.Services.Client, which keeps this otherwise-clean worker coupled to the legacy WCF estate; the 270-day threshold is hardcoded rather than configurable.