Actions
Issue #5012
closedssl_client_key printed in the logs
Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 57
Quarter:
Description
I noticed that when I performa PATCH request to update a FIle Remote, the ssl_client_key is printed in the logs at INFO level.
Actions
Prevent rq from logging secrets
Though the issue is specific about certain cases that shouldn't be logged, we do not have fine control over what rq logs, so the solution is to disable logging of the description (which includes the job arguments).
https://pulp.plan.io/issues/5012 fixes #5012