SCRAPE-20: Implement credential redaction in scraper log calls #24

Merged

stephen merged 1 commits from scraper/log-audit into dev

2026-02-06 23:00:09 -07:00

Author	SHA1	Message	Date
Stephen Minakian	ba09cdf8ec	Replace console.error calls in scraper admin routes with structured scraperLogger All checks were successful CI/CD Pipeline - Apartment API / Lint & Test (pull_request) Successful in 41s Details CI/CD Pipeline - Apartment API / Send Webhook Notification (pull_request) Successful in 2s Details CI/CD Pipeline - Apartment API / Build & Push Image (pull_request) Has been skipped Details CI/CD Pipeline - Apartment API / Deploy to Production (pull_request) Has been skipped Details CI/CD Pipeline - Apartment API / Scan Dependencies (pull_request) Successful in 13s Details 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.	2026-02-06 22:57:33 -07:00