Skip to content

fix(config): strip logFile and logLevel from project config - #115

Merged
jlrickert merged 1 commit into
mainfrom
fix/project-config-logging
Sep 27, 2026
Merged

jlrickert merged 1 commit into
mainfrom
fix/project-config-logging

Conversation

@jlrickert

Copy link
Copy Markdown
Owner

Summary

A repository's .tapper/config.yaml could set logFile, which tap opens for append on every command, including the auto-started tap mcp. Cloning a hostile repo could therefore point Tapper at a shell rc file. Logging is now user-config only, like hubs and relay, and a stripped value produces a load warning.

Changes

  • pkg/tapper/config.go: project config drops logFile/logLevel with a warning
  • schemas/tap-config.json and docs/configuration/resolution-order.md updated
  • Tests cover the strip and the warning

Testing

  • go build, go vet, go test ./..., -race for keg/tapper/parity
  • task lint:docs, task lint:fs

A repository's .tapper/config.yaml could set logFile, which tap opens for
append on every command, including the auto-started tap mcp. A cloned repo
could therefore target a shell rc file. Logging is now user-config only,
like hubs and relay, and a stripped value produces a load warning.
@jlrickert
jlrickert merged commit ccab152 into main Sep 27, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant