Repository navigation
rustybuns: set redact_query_string in the upload once Alchemy passes it #605
Description
Follow-up to #553. Alchemy 2.0.0-beta.77's Worker upload schema (from @distilled.cloud/cloudflare) has no redact_query_string in observability, so it gets dropped, and every script upload resets the flag to false. For now rustybuns deploy PATCHes script-settings after each deploy (packages/cli/src/redact.ts). That leaves a few seconds per deploy where query strings are logged, and a deploy without a CLOUDFLARE_API_TOKEN only warns.
Once Alchemy's WorkerObservability takes redactQueryString, emit it in gen/alchemy.ts and drop the post-deploy step.
Metadata
Metadata
Assignees
Labels
No labels
Activity
QuinnsCode commentedon Oct 11, 2026
Status 2026-10-11: still blocked.
2.0.0-beta.81(we're on beta.77). It pins@distilled.cloud/cloudflare@1.0.0-rc.13.redactQueryStringon the script-settings schemas, but not on the upload'sPutScriptMetadataObservability, which is what Alchemy'sWorkerObservabilityis derived from. So it would still be dropped on upload, and the post-deploy PATCH inpackages/cli/src/redact.tsstays.What to watch:
@distilled.cloud/cloudflare:PutScriptMetadataObservabilityinsrc/services/workers.tsgainingredactQueryString. That package is generated from Cloudflare's API spec, so the real trigger may be Cloudflare addingredact_query_stringto the upload metadata schema.alchemyrelease pinning that distilled version. No Alchemy code change is needed, because the type flows straight through.Nobody needs to watch by hand: PR #714 adds a typecheck tripwire (
apps/codesplitters/test/alchemy-redact.typecheck.ts) that fails the Alchemy bump PR once the field exists. When it fires, emitredactQueryString: trueingen/alchemy.ts, dropredact.ts/redactAfterDeploy/ its test and the tripwire, deploy once and confirm the flag stays on after the upload, then close this.codeSplitters: typecheck tripwire for Alchemy taking redactQueryString (
Alchemy 2.0.0-beta.84 with provider packages, effect 4.0.5, DO_NOT_TR…