rgw: use trace logs for RGW admin HTTP info #8937
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Debug logs for the RGW Admin Ops debugHTTPClient can leak credentials
used to access the Admin Ops API as well as credentials that may be
returned for any buckets/users. Use trace logs instead, which users are
unlikely to enable in production to mitigate the risk.
This is a partial backport of #8808. Including
TRACE_LOGGING
proved challenging given how much the controller code changed between 1.7 and master, but changing the leaky debug logs to trace is simple.Signed-off-by: Blaine Gardner blaine.gardner@redhat.com
Description of your changes:
Which issue is resolved by this Pull Request:
Resolves #
Checklist:
make codegen
) has been run to update object specifications, if necessary.