SCRAPE-20: Implement credential redaction in scraper log calls #24
Reference in New Issue
Block a user
No description provided.
Delete Branch "scraper/log-audit"
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?
Replaced 4 raw console.error calls in scraper admin routes with structured scraperLogger calls using createLogger. Error objects sanitized to log error.name and error.message instead of raw objects, preventing credential leakage. All scraper production code now uses scraperLogger with built-in credential redaction.
Replace 4 raw console.error calls in the scraper admin routes (trigger, status, history, config endpoints) with structured scraperLogger calls using createLogger('scraper-admin'). Error objects are now sanitized to log error.name and error.message instead of raw error objects, ensuring credential redaction is applied consistently across all scraper production code paths.