reconsent-ui
Angular 17 single-page app where customers review and update their marketing/travel consent preferences, backed by reconsent-api.
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 | typescript |
| Frameworks | Angular 17, Angular Material, Bootstrap 5 |
| Runtimes | node |
| Tests / CI | some / CI in place |
| Last commit | 2025-10-08 |
| 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 | 2 release pipeline(s): \marketing\reconsent-ui; \marketing\reconsent-ui master |
| Integration | rest |
| Source | Open in Azure DevOps |
Dependencies in context
Entanglement
loose No binding mechanisms apply: this system needs no untangling work.
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
A long roadTechnically eligible one day, but the blockers are structural: hosted WCF or SOAP contracts that cannot run two versions at once, or heavy legacy coupling. Sequence the modernisation work first. Legacy web front end: session state and framework age make mixed-version fleets risky until state is externalised.
- 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.
- Externalise any remaining session state so users can move between nodes mid-session without disruption.
- 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
Rotate the credentials committed to reconsent-ui
Risk flags indicate credentials or keys in source (hardcoded-secrets). Rotate now and enable secret scanning in CI; this is independent of all other work.
Impact: Closes a live security exposure at near-zero cost
proposedAssessment notes
reconsent-ui
Purpose
Customer-facing reconsent journey ("ReconsentApp"): contact details, preference toggles and confirmation pages that read and write consent state through the Reconsent API. Multi-language via ngx-translate with translation assets, plus a client-side error-reporting service posting to the shared webapi-exceptions endpoint.
Tech stack
Angular 17 with Angular Material 17, Bootstrap 5.3, RxJS 6 and the internal @tc/web-icons package; Sass styling, ESLint + husky/lint-staged, Karma/Jasmine unit tests and a legacy Protractor e2e folder. Served from IIS (a web.config ships in src).
Deployment
Included as prod_application with 2 releases (\marketing\reconsent-ui, \marketing\reconsent-ui master) from build pipelines reconsent-ui and reconsent-ui CI. YAML pipeline uses the shared azure-pipelines-templates repo but still pins nodeVersion: 12.x, far below what Angular 17 requires. Deployment is classic IIS via PowerShell scripts in deployment/ with a Slack webhook notification.
Dependencies
Internal: calls reconsent-api (ReconsentAPI/api on appservices.travelcounsellors.com) and the shared Phenix webapi-exceptions error service. No third-party runtime services.
Data stores
None — purely a browser SPA; all state lives behind the API.
Integration points
Outbound REST to the Reconsent API with an apiKey GUID sent from the client, and error reporting to the exceptions endpoint. Production API base is plain http://.
Code health
13 Jasmine spec files with service stubs — reasonable unit coverage for the app's size, though the Protractor e2e setup is deprecated tooling. README is the stock Angular CLI text. Last commit 2025-10-08; the framework was kept current (Angular 6 origin upgraded to 17).
Modernisation risks
Low overall: modern Angular with tests and CI. Issues worth fixing: the API key committed in environments/*.ts (client-side keys are visible anyway, but it shouldn't gate anything sensitive), plain-HTTP production API base, the node 12 pin in the pipeline, and Protractor e2e that can no longer run on supported tooling.