Repository navigation
relay: the production config keeps prod's CAF_LIMITS - #2214
Merged
Merged
Conversation
The live production relay (caf-fabric) runs with
CAF_LIMITS={"globalNewIdentitiesPerDay":10000,"globalStoreBytes":1099511627776},
set when it was deployed by hand. The generated production config had no
CAF_LIMITS, so the first CI deploy to production would have removed both
deployment-wide brakes. The production channel now emits exactly that value;
staging and dev emit none, as before.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The live production relay Worker (
caf-fabric) runs withCAF_LIMITS={"globalNewIdentitiesPerDay":10000,"globalStoreBytes":1099511627776}, set when it was deployed by hand.scripts/relay-wrangler-config.sh productionemitted noCAF_LIMITS, so the first CI deploy to production (onceRELAY_DEPLOY_PRODUCTIONistrue) would have removed both deployment-wide brakes:limits.jstreats a missing value as no cap.The production channel now emits exactly the live value. Staging and dev emit none, as before.
Changes Made
scripts/relay-wrangler-config.sh: per-channelcaf_limits, written into[vars]for production only (also replaces aCAF_LIMITSline if the basewrangler.tomlever gains one)scripts/relay-wrangler-config_test.sh: production carries the exact value; staging and dev carry noneNo relay code and no binary change. The config generator runs only in the release workflow's relay job.
Test Plan
bash scripts/relay-wrangler-config_test.shpasses, as dorelay-deploy_test.shandrelay-fingerprint_test.sh(themake test-toolingrelay checks)wrangler deploy --dry-run; its bindings match the live production Worker plus the two machine-door rate limits from fix(relay): harden the machine doors #2073 put on the hosted relay #2076🤖 Generated with Claude Code