phenix-thememanager
Small .NET 8 API for viewing, editing and adding documentation themes (standard image sets), proxying theme operations to the booking documentation 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 | none / CI in place |
| Last commit | 2025-02-19 |
| Owner | Owner unknown (mapping to be curated) |
| Domain | Content and destinations (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): [deprecated] phenix-thememanager CI; \cx\phenix-thememanager |
| Integration | rest, wcf |
| 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
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. No automated tests yet.
- 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
phenix-thememanager
Purpose
Backend for the Phenix Theme Manager, a small admin app for viewing, editing and adding "themes" — sets of standard images (preview, business card, banner) used in booking documentation. The Angular frontend lives in the phenix-ui monorepo; this repo is the API only.
Tech stack
C# on .NET 8 (TC.ThemeManager.Api, single project in the solution), ASP.NET Core with Swashbuckle 7 Swagger, PhenixAuth.AspNetCore authentication (target PhenixThemeManager), TravelCounsellors.ApiTools for CORS setup, and TC.ConnectionBroker 1.15 (Api + Wcf) for outbound calls.
Deployment
Included as prod_application with 2 releases. Build pipelines: phenix-thememanager, thememanager-site release and a deprecated CI pipeline; release pipelines: \cx\phenix-thememanager plus the deprecated CI. Repo contains azure-pipeline.yaml using the shared InternalOSS/azure-pipelines-templates CI template (dotnet SDK 8.x). Hosted under IIS as a sub-application (web.config with AspNetCoreModuleV2, per-environment web.*.config transforms) at /api/phenix-thememanager.
Dependencies
Internal packages: TC.ConnectionBroker.* (tc-connectionbroker), TC.Documentation.Booking.Contract (backoffice-documentation-booking, the WCF contract it consumes), TravelCounsellors.ApiTools (tc-api-tools), plus PhenixAuth.AspNetCore.AuthenticationScheme. No third-party external services.
Data stores
None owned. All theme data lives behind the booking documentation service; this API holds no connection strings (appsettings.json is essentially empty).
Integration points
Inbound REST (single DataController with Swagger, all endpoints require authorization). Outbound WCF to the booking documentation service via TC.ConnectionBroker.Wcf ClientBaseWrapper.
Code health
No test projects at all. YAML CI exists and uses shared templates. Codebase is tiny (one controller, one service client) but carries template leftovers (WeatherForecast.cs). Last commit 2025-02-19 — quiet but not abandoned. README is short but accurate, with environment URLs.
Modernisation risks
Already on .NET 8, so the runtime is fine; the main liability is the WCF client dependency on the legacy booking documentation service, which ties this API to that service's modernisation path. No tests means regressions would only surface in QA. Low priority overall — small, modern, and easily re-pointed if the documentation service gets a REST facade.