tc-public-quote-sync-service
.NET 6 sync service that imports quotes built in the public/myTC quote system into Phenix — transforming public quote itineraries, costs and documents into Phenix quote records and notifying the customer.
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 6, AutoMapper 12, RestEase, SkiaSharp |
| Runtimes | .NET 6 |
| Tests / CI | some / CI in place |
| Last commit | 2026-07-21 |
| Owner | Owner unknown (mapping to be curated) |
| Domain | Selling and quoting (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): \cx\tc-quote-sync-service; \cx\tc-quote-sync-service Stealth |
| Integration | rest, wcf |
| Source | Open in Azure DevOps |
Risk flags
Each flag links to its glossary definition.
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
Needs workFeasible through the Workflow Engine's rolling drain, but real preparation is needed: dual-version discipline, better tests, or schema care before at-will release is sensible. Legacy runtime: the rolling drain works (stealth releases prove it) but relies on fix-forward risk rather than dual-version safety.
- Consumes WCF contract packages: never take a breaking client bump mid-feature, and treat obsolete warnings as migration debt
- 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
Replatform tc-public-quote-sync-service to modern .NET
Runs on .NET 6, out of mainstream support. No pinning dependency blocks it; sequence by fan-in (providers before consumers).
Impact: Reduces the end-of-life runtime count
proposedAssessment notes
tc-public-quote-sync-service
Purpose
Bridges the public quote world (myTC/customer portal) and Phenix: a Quote/Import endpoint accepts folder/quote IDs, queues them through an in-process channel and hosted service, fetches the public quote, transforms it via an extensive factory layer (Db* models for every itinerary item type, cost breakdowns, documents, images, themes) into a Phenix quote, pushes it through the public quote API, marks sync completion, and optionally sends a push notification to the customer.
Tech stack
C# on .NET 6 — the API host targets net6.0-windows (Windows-bound), the libraries plain net6.0. ASP.NET Core with a single controller, System.Threading.Channels queue + ImportQuoteHostedService, AutoMapper, RestEase, SkiaSharp for image handling, TC.ConnectionBroker (Api/Sql/Wcf), TC.Cognito.Auth.Client, Swashbuckle, TC.Diagnostics health checks.
Deployment
Included as prod_application with 2 releases: \cx\tc-quote-sync-service and \cx\tc-quote-sync-service Stealth, from build tc-quote-sync-service CI (YAML via shared templates, SDK 6.x). Per-environment appsettings (testqa, qa, training, preproduction, production, liveproviderqa, datafixqa).
Dependencies
Wide internal surface: TC.Phenix.Quote.ServiceContract (phenix-quote), TC.ServiceContract.Linking (phenix-linking-service), TC.Phenix.PlaceRepository (phenix-place-repository), TC.DestinationManagement.API.Client (phenix-destination-management), TC.Flights.Domain (phenix-flights), TC.Documentation.Booking.Contract (backoffice-documentation-booking), TC.PushNotifications.Contract (backoffice-pushnotifications-api), TC.CustomerPortalUsers.ServiceContracts (mytc-user-service), TC.Exceptions.WebApiClient.AspNetCore (webapi-exceptions), TC.ConnectionBroker.* (tc-connectionbroker), plus TC.Phenix.Services.Client, TC.Phenix.ClientApiLibrary, TC.Storage.Client and TC.Documentation.Quote.ResourceStrings (source repos not confirmed). External: AWS Cognito for outbound auth.
Data stores
No owned database. A SQL connection broker is registered but data access goes through Phenix WCF/REST services (quote, public quote, booking, linking, reviews, assets, themes clients under Services/).
Integration points
Inbound REST (Quote/Import, Swagger); outbound REST to public quote, push notifications, public assets/reviews APIs via brokered HTTP clients; outbound WCF to Phenix quote/booking/linking/customer-portal services via ConnectionBroker.Wcf.
Code health
One test project (PublicQuoteFactory.Tests) with ~45 tests covering the transformation factories — the riskiest logic — but nothing on the queue, importer or service clients. README is untouched boilerplate. Actively developed (last commit 2026-07-21) yet still on .NET 6, which went end-of-life in November 2024.
Modernisation risks
Medium: the runtime is EOL and the API host is pinned to net6.0-windows, so an upgrade to .NET 8 plus removal of the Windows-only dependency is due; it also spans a very wide legacy WCF client surface across quote, booking and linking services, making it sensitive to any Phenix WCF decommissioning. The in-memory import queue means queued imports are lost on restart.