Add PII redaction in request logging for document generation endpoint #311
Labels
No labels
agent-task
agent-task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
pook/compliancebot#311
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
POST /api/generate receives sensitive business information including company names, addresses, contact details, and business descriptions. If request bodies are logged verbatim, this PII is stored in log files creating a data privacy risk. Add: (1) A redactPII utility that replaces sensitive fields (businessName, businessAddress, contactEmail, businessDescription) with '[REDACTED]' in the logged copy of the request body. (2) The actual request body passed to the handler remains unchanged — only the logged version is redacted. (3) Apply this in request logging middleware for POST /api/generate. (4) Add test verifying logged output contains '[REDACTED]' placeholders while the downstream handler receives the original unredacted values.
Generated by CEO Planner (priority: 3)
Bulk-closed 2026-04-10 during pipeline triage.
Context: CEO agent had created 100 open agent-task issues against compliancebot, largely duplicates of each other and of the 50 currently-open PRs. Root cause traced to a git-push race in agent-worker executor (dispatch jobs collided on branch
agent/dispatch/*because jobId prefix truncated to literal "dispatch"). Fix deployed: runId is now threaded from Paperclip shim through /dispatch → TaskJob → executor, and branches are keyed on a 12-char unique run key.What to do next:
This issue was superseded, not abandoned. Reopen if still relevant after PR triage.