Production Launch Checklist
Items deferred until production infrastructure is stood up. Until then, PPP runs on UAT only (the ppp-uk-uat Pulumi stack + ppp-dev Cloudflare tunnel + GitHub Pages docs); the only prod surface is the marketing site.
Tracked here so we don't lose them in the issue queue. When the ppp-uk-prod stack is provisioned and a real production launch begins, walk this list top to bottom.
How to use this list
- One item = one production-readiness gate. Each item names the source code, the activation step, and an acceptance criterion you can tick when done.
- Add items here, not as
for-discussionGH issues. Issues age and clutter the queue; this checklist persists. - When you action an item: open a small focused PR that performs the activation, link to the relevant section here, and tick the box.
Container Apps & scheduled jobs
[ ] CPD reminder Container Apps Jobs — enable in
ppp-uk-prod(was tracked as #5709)Source:
api/infra-azure/src/index.tslines ~1107–1300 — the 4 CPD reminder jobs (cpd-plan-reminder,cpd-submission-prompt,cpd-deficit,cpd-milestone) plus the AMC review job (super-admin-amc-review) are gated onif (environment === 'uat') { ... }. Lift the gate (or extend it to'uat' | 'prod') when prod is ready.Pre-conditions before lifting the gate:
- [ ] Production database has the
cpd_reminder_settingstable seeded (migration0057applied +seedCpdReminderSettings.tsrun) - [ ] Production secrets (Azure Key Vault) carry the same env vars as UAT — verify via
pulumi config getagainst theppp-uk-prodstack - [ ]
super_adminrole is granted to a known PPP-staff account in production (so the Super Admin console works) - [ ] Send-test-to-me works end-to-end against a production email recipient
- [ ]
cpd_reminder_settings.enabled = falsefor all 4 reminders at first deploy, so the jobs spin up empty and we observe their telemetry before any user-facing notifications fire - [ ] Application Insights dashboards / alerts exist for each job's success rate, duration, and notification count
- Once gates green: open a small PR removing/widening the
if (environment === 'uat')guard. Spec ref:cpd.md § Production wiring — Azure Container Apps Jobs
When done: tick this box, link the activation PR here, close any tracking issue.
- [ ] Production database has the
Folded from closed issues (2026-06-01)
[ ] Repair the
pppProdCloudflare Pulumi stack before first prod DNS deploy (was #7900)Source:
api/infra-cloudflare/— the Cloudflare Pulumi program (DNS, Pages, R2). ThepppProdstack state is corrupted: thepages_domainresource is missing itsdomainattribute, sopulumi preview/uperrors before any prod DNS can be deployed.Pre-conditions / repair procedure (full runbook preserved in the closed issue's comments: #7900):
- [ ] Export the
pppProdstack state (pulumi stack export) - [ ] Patch the corrupted
pages_domainresource to restore the missingdomainattribute - [ ] Re-import the patched state (
pulumi stack import), thenpulumi refresh - [ ] Run
pulumi upto reconcile - [ ] Confirm the R2 bucket
ppp-member-assetsand its sync token are present as intended-for-prod creates (not accidental diffs)
Acceptance:
pulumi previewon thepppProdstack is clean (no error, no unexpected diff) and the apex domain is IaC-deployable.When done: tick this box, link the activation PR here.
- [ ] Export the
[ ] Cloudflare WAF + production rate-limiting in front of the tRPC API (was #7318)
Source:
api/infra-cloudflare/— add a managed WAF ruleset and a rate-limit profile to the Cloudflare Pulumi program, scoped to the production API hostname.Pre-conditions:
- [ ] Production API hostname (the prod equivalent of the UAT tRPC endpoint) is provisioned and routed through Cloudflare
- [ ] WAF managed ruleset configuration is reviewed against the tRPC traffic profile (avoid false-positive blocks on legitimate API calls)
- [ ] Rate-limit thresholds agreed for the prod API hostname (per-IP request budget, burst, block duration)
Acceptance: a managed WAF ruleset and a rate-limit profile are active on the prod API hostname.
When done: tick this box, link the activation PR here.
[ ] Regenerate real SHA-256 SPKI pins before the first production mobile release (was #5110)
Source: the mobile certificate-pinning config in
mobile/ppp/— the current pins are placeholders/dev values and must be replaced with pins computed from the real production certificate chain.Pre-conditions:
- [ ] The production API hostname's leaf and intermediate certificates are issued and stable
- [ ] SHA-256 SPKI pins are computed from the real prod leaf and intermediate certs (include a backup pin for rotation)
- [ ] The pinning config in
mobile/ppp/is updated with the new pins
Acceptance: the pins match the real prod leaf/intermediate certs and pin-validation passes against prod.
When done: tick this box, link the activation PR here.
[ ] Set up the production Whoop OAuth app before prod wellness deploy (was #4700)
Source: the Whoop OAuth wiring in
api/backend-pppwellness (OAuth deep-link / callback handling) plus Azure Key Vault for the client credentials.Pre-conditions:
- [ ] A production Whoop OAuth application is registered with the prod redirect/callback URLs
- [ ] The prod Whoop client id and secret are stored in the production Azure Key Vault (not reusing the UAT app's credentials)
- [ ] The wellness OAuth config resolves the prod credentials in the
ppp-uk-prodenvironment
Acceptance: prod Whoop client id/secret live in the prod Key Vault and an OAuth round-trip works against prod.
When done: tick this box, link the activation PR here.
Future entries
When the production stack is being stood up, additional gates will land here. Candidate areas (none of them committed yet, just signposting):
- Application Insights production workspace + dashboards + alerts
- Production database backup + point-in-time restore drill
- Stripe live mode key rotation + webhook signing secret in prod Key Vault (#5140)
- Azure AD B2C production tenant or equivalent identity provider
- Mobile app store production builds (Apple Developer + Google Play production channels)
- Production-tier DNS + email reputation (SPF, DKIM, DMARC) for
professionalperformanceportfolio.com - Compliance: Australian Privacy Act mapping + AHPRA notification mailbox + APHRA legal sign-off (deploy gate from #5710)
Add each as a checklist item with the same shape — source, pre-conditions, acceptance — when the relevant feature work makes it concrete.