reconsent-api
Small ASP.NET Core 8 API that lets customers update their marketing and travel preferences (GDPR reconsent), proxying reads and writes to the contact-centre WCF service.
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 |
| Runtimes | .NET 8 |
| Tests / CI | some / CI in place |
| Last commit | 2026-07-20 |
| 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 | On-prem Deployed to our own machines
|
| Releases | 1 release pipeline(s): \marketing\reconsent-api |
| Integration | rest, wcf-client |
| 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
- 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
reconsent-api
Purpose
Backend for the customer reconsent journey. Two controllers — ContactController and PreferencesController — expose contact lookup and preference updates; a domain library wraps the contact-centre service client in ContactCentreServiceManager / PhenixContactCentreServiceManager so consent changes land in the shared contact-centre system.
Tech stack
C# on .NET 8 (two SDK-style projects plus a test project). Swashbuckle 6.8 with API versioning, TC.Common.Hypermedia for HATEOAS-style responses, TC health-check extensions, TC.Exceptions middleware, and System.ServiceModel.Http 8.x for the WCF client. Nerdbank.GitVersioning (version.json) drives versioning.
Deployment
Included as prod_application with 1 release via \marketing\reconsent-api from build pipeline reconsent-api. YAML azure-pipelines.yml in the repo using the shared azure-pipelines-templates CI template — though it still pins SDK 6.0.x while the projects target net8.0.
Dependencies
Internal packages: TC.ConnectionBroker.Api/Wcf (tc-connectionbroker), TC.Exceptions.* (tc-exceptions), and TC.ContactCentre.ServiceClient (phenix-contact-centre-wcf). No third-party services.
Data stores
None owned. The README documents scaffolding an EF context against TravelCounsellorWebDetail, but no DbContext or SQL access survives in the current code — all data goes through the contact-centre service.
Integration points
Inbound versioned REST with Swagger; outbound calls to the legacy contact-centre service over the WCF/SOAP client via ConnectionBroker.
Code health
One test project covering the contact-centre service manager — some coverage but narrow. Actively maintained (last commit 2026-07-20) with a genuine README. One appsettings variant is UTF-16 encoded, a small oddity. Modern dependency versions throughout.
Modernisation risks
Low: modern .NET 8 REST API with CI and some tests. The main residual risk is its hard dependency on the .NET Framework-era contact-centre WCF/ASMX service — this API inherits whatever migration plan that service gets — plus the stale SDK pin in the pipeline.