Issue #5012
closed
ssl_client_key printed in the logs
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.
Updated by amacdona@redhat.com over 5 years ago
- Triaged changed from No to Yes
- Sprint set to Sprint 55
Updated by dkliban@redhat.com over 5 years ago
- Sprint changed from Sprint 55 to Sprint 56
Updated by amacdona@redhat.com over 5 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to amacdona@redhat.com
Added by amacdona@redhat.com over 5 years ago
Updated by amacdona@redhat.com over 5 years ago
- Status changed from ASSIGNED to MODIFIED
Applied in changeset ansible-pulp3|a6fd4fbda0302d1ed24215fc7d718d00c7cbd036.
Updated by amacdona@redhat.com over 5 years ago
- Status changed from MODIFIED to POST
Added by amacdona@redhat.com over 5 years ago
Revision a1838b13 | View on GitHub
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).
Added by amacdona@redhat.com over 5 years ago
Revision a1838b13 | View on GitHub
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).
Updated by amacdona@redhat.com over 5 years ago
- Status changed from POST to MODIFIED
Applied in changeset ansible-pulp3|a1838b13a37b21b5b0d76178f3a0fbbdeb52291b.
Updated by bmbouter about 5 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
.
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