ci(cloud-agent-next): add staging worker config#4117
Conversation
| "bucket_name": "kilocode-sessions-staging", | ||
| }, | ||
| ], | ||
| "hyperdrive": [], |
There was a problem hiding this comment.
WARNING: Staging loses GitHub App installation lookup
This env removes the HYPERDRIVE binding, but prepareSession only resolves repository installations when Hyperdrive is configured (services/cloud-agent/src/router/handlers/session-prepare.ts, lines 96-144). Any staging caller that sends githubRepo without an explicit githubToken will now fail with GitHub token or active app installation required for this repository, so repo-backed staging sessions won't behave like production.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (2 files)
Previous Review Summary (commit b82c40c)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit b82c40c)Status: 1 Issue Found | Recommendation: Address before merge Fix these issues in Kilo Cloud Overview
Issue Details (click to expand)WARNING
Other Observations (not in diff)No additional findings outside the diff. Files Reviewed (1 files)
Reviewed by gpt-5.4-20260305 · 171,344 tokens Review guidance: REVIEW.md from base branch |
|
Closing in favor of #4118, which is based directly on main and contains only the cloud-agent-next staging config change. |
Summary
Adds an explicit
stagingWrangler environment forservices/cloud-agent-nextso it can participate in the staging Worker deployment matrix without reusing production routes, queues, R2 buckets, or container capacity.Verification
Manual verification was limited to local config inspection and Wrangler dry-run behavior; live Cloudflare resource checks were blocked because local Wrangler auth does not have access to the configured Kilo Cloudflare account.
Visual Changes
N/A
Reviewer Notes
This PR targets
foamy-dripso the diff only contains the cloud-agent-next staging configuration layered on top of the staging deployment workflow PR.The staging config points service bindings at staging-named dependencies (
session-ingest-staging,git-token-service-staging,notifications-staging) so staging traffic is not silently routed to production workers. Those dependency deployments must exist before a live deploy can fully succeed.