docs(phase4): Cloud Run activation prompt + mark Phase 4 merged#105
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
✅ Files skipped from review due to trivial changes (3)
WalkthroughThis PR adds documentation to support Phase 4 production activation. It introduces a new Cloud Run activation runbook that documents the current infrastructure state (deployment, service URL, service account, Cloud Tasks queue, GCS bucket configuration, and IAM permissions), specifies the exact command to set four missing environment variables and increase request timeout to 600, and includes verification steps (OIDC check plus end-to-end upload test) and a rollback command. Supporting updates mark Phase 4 code as merged in the progress tracker and update the Cloud Tasks README to reference the new activation documentation and clarify that the GCS bucket variable is already configured. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
f30c05d to
e47f163
Compare
Phase 4 — activation docs
Phase 4 (async upload processing via Cloud Tasks) is merged (#99, #102, #101). This adds the maintainer-facing activation guidance and updates the trackers. Docs only — no code changes.
What changed
docs/plans/2026-06-06-phase4-cloud-run-activation.md— a verified, copy-paste agent prompt to finish prod activation (set the 4 Cloud Tasks env vars + raise the Cloud Run timeout to 600), plus a live-state table and a smoke-test checklist.infra/cloud-tasks/README.md— links to the activation doc and corrects the now-stale note (GCS_UPLOAD_BUCKETis already set on the service; Phase 3 storage is active).docs/plans/2026-05-31-large-upload-gcs-resumable-plan.md— Phase 4 tracker marked merged, with a pointer to the activation doc.Verified live state (from gcloud, kept OUT of the committed docs)
The code is already deployed (image
0e42895=mainHEAD; auto-deploy via Cloud Build); queue, invoker SA, bucket, and all IAM bindings exist; only the 4 env vars + timeout remain.Privacy
This is a public repo. The live Cloud Run URL, gcloud account, and unrelated project name are intentionally not committed — the prompt resolves the service URL at run time via
gcloud run services describe. Sensitive-literal scan + markdownlint + docs-check + security-check all clean.