-
Notifications
You must be signed in to change notification settings - Fork 5.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
br: redact ak/sk in logging (#55622) #55780
br: redact ak/sk in logging (#55622) #55780
Conversation
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## release-7.5 #55780 +/- ##
================================================
Coverage ? 72.0935%
================================================
Files ? 1415
Lines ? 412940
Branches ? 0
================================================
Hits ? 297703
Misses ? 95354
Partials ? 19883
Flags with carried forward coverage won't be shown. Click here to find out more.
|
[LGTM Timeline notifier]Timeline:
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 3pointer, BornChanger, YuJuncen The full list of commands accepted by this bot can be found here. The pull request process is described here |
This is an automated cherry-pick of #55622
What problem does this PR solve?
Issue Number: close #55273
Problem Summary:
log-backup: secrets may be directly logging to log when --send-credentials-to-tikv=false not set during starting log backup
What changed and how does it work?
Added a wrap of the storage info and redact ak/sk, now the logging woud not print them directly.
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.