ci(cloud-agent-next): add staging worker config#4118
Conversation
![kilo-code-bot[bot]](https://avatars.githubusercontent.com/in/2193792?s=60&v=4){kind=small}
| "services": [ | ||
| { | ||
| "binding": "SESSION_INGEST", | ||
| "service": "session-ingest-staging", |
There was a problem hiding this comment.
WARNING: Staging dependencies are not declared in this repo
cloud-agent-next now binds to session-ingest-staging, git-token-service-staging, and notifications-staging, but this repo only defines session-ingest, git-token-service/git-token-service-dev, and notifications. That means the new staging environment depends on out-of-band worker provisioning and cannot be reproduced from main; if those workers are not already deployed separately, the staging worker will fail to resolve its service bindings.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
Code Review SummaryStatus: 1 Issue Found | Recommendation: Address before merge Overview
Fix these issues in Kilo Cloud Issue Details (click to expand)No new issues found in the incremental diff. Other Observations (not in diff)Issues found in unchanged code that cannot receive inline comments:
The previously reported Files Reviewed (1 files)
Previous Review Summaries (3 snapshots, latest commit 8673ee2)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 8673ee2)Status: 1 Issue Found | Recommendation: Address before merge Overview
Fix these issues in Kilo Cloud Issue Details (click to expand)WARNING
Other Observations (not in diff)The previously reported Files Reviewed (4 files)
Previous review (commit b9a4b20)Status: 1 Issue Found | Recommendation: Address before merge Overview
Fix these issues in Kilo Cloud Issue Details (click to expand)WARNING
Other Observations (not in diff)No additional issues found outside the diff. Files Reviewed (1 files)
Previous review (commit 57fcc47)Status: 1 Issue Found | Recommendation: Address before merge Overview
Fix these issues in Kilo Cloud Issue Details (click to expand)WARNING
Other Observations (not in diff)No additional issues found outside the diff. Files Reviewed (1 files)
Reviewed by gpt-5.4-2026-03-05 · 273,981 tokens Review guidance: REVIEW.md from base branch |
| "r2_buckets": [ | ||
| { | ||
| "binding": "SESSION_INGEST_R2", | ||
| "bucket_name": "session-ingest-staging", |
There was a problem hiding this comment.
WARNING: Staging shares the same R2 bucket as the default environment
env.staging still points SESSION_INGEST_R2 at session-ingest-staging, which is the same bucket the default session-ingest worker already uses. That means staging ingest traffic can mix uploaded session data and any bucket-level cleanup with the live environment instead of staying isolated.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
1 participant
Summary
Adds explicit
stagingWrangler environments forservices/cloud-agent-nextand the service-binding dependencies it needs to deploy cleanly:git-token-service,session-ingest,notifications, andevent-service.The staging Cloud Agent Next Worker uses the custom domain
staging.cloud-agent-next.kilosessions.ai, isolated staging queues/R2/container capacity, and staging-named service bindings so staging deploy validation does not silently bind to production workers.Verification
Manual verification was limited to Wrangler dry-run behavior for the staging Worker graph. Live Cloudflare deploys require pre-created named queues/R2 buckets and authenticated Wrangler access to the Kilo Cloudflare account.
Visual Changes
N/A
Reviewer Notes
Deploy dependency order:
event-service-staginggit-token-service-stagingsession-ingest-stagingnotifications-stagingcloud-agent-next-stagingsession-ingest-stagingstill binds to the existingo11yservice. A fully isolated staging observability stack would require separate Analytics Engine/Pipelines/secrets and is intentionally left out of this PR.