fix(gastown): stop logging town config secrets#3649
Open
evanjacobson wants to merge 3 commits into
Open
Conversation
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Executive SummaryAll three new commits cleanly resolve both pre-existing warnings: Resolved Issues (previously open)
Incremental Review (commits since bf16ab1)Commits reviewed:
Files Reviewed (10 files)
Reviewed by claude-sonnet-4.6 · 986,157 tokens Review guidance: REVIEW.md from base branch |
bf16ab1 to
8925f76
Compare
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
Cloudflare request logs could expose credential-bearing town config because the container control plane sent full config through
X-Town-Configheaders. This keeps startup/config-sync behavior intact while moving secrets and custom env vars onto non-header paths.Details
X-Town-Configto carry only non-secret town context.Verification
No manual verification; this is a backend-only container config propagation change with no UI or visual behavior.
Visual Changes
N/A
Reviewer Notes
Focus areas: secret-bearing fields should stay out of headers, and model hot-swap/start/merge paths should continue receiving credentials through body/env-var paths.