br: redact ak/sk in logging

[RidRisR]

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

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

Added a wrap of the storage info and redact ak/sk, now the logging woud not print them directly.

[tiprow]

Hi @RidRisR. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.6153%. Comparing base (99180a8) to head (7c3e52b).
Report is 49 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #55622        +/-   ##
================================================
+ Coverage   72.9575%   75.6153%   +2.6578%     
================================================
  Files          1577       1585         +8     
  Lines        440885     452322     +11437     
================================================
+ Hits         321659     342025     +20366     
+ Misses        99480      89572      -9908     
- Partials      19746      20725       +979     

Flag	Coverage Δ
integration	50.4932% <100.0000%> (?)
unit	72.0507% <100.0000%> (+0.0182%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	52.9567% <ø> (ø)
parser	∅ <ø> (∅)
br	60.2277% <100.0000%> (+14.2817%)	⬆️

[YuJuncen]

compilepkg: nogo: errors found by nogo during build-time code analysis:

pkg/util/redact/redact.go:240:7: unused-receiver: method receiver 't' is not referenced in method's body, consider removing or renaming it as _ (revive)

pkg/util/redact/redact.go:236:6: exported: exported type TaskInfoRedacted should have comment or be unexported (revive)

Would you fix those linter problems?

[RidRisR]

/test unit-test

[RidRisR]

/test build

[tiprow]

@RidRisR: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test unit-test

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[tiprow]

@RidRisR: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test build

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[RidRisR]

/test pull-br-integration-test

[tiprow]

@RidRisR: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test pull-br-integration-test

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Leavrth, YuJuncen

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [Leavrth,YuJuncen]
• br/OWNERS [Leavrth,YuJuncen]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-08-28 02:26:35.18819917 +0000 UTC m=+923590.322649288: ☑️ agreed by Leavrth.
• 2024-08-28 02:44:23.588631313 +0000 UTC m=+924658.723081434: ☑️ agreed by YuJuncen.

[RidRisR]

/test unit-test

[tiprow]

@RidRisR: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test unit-test

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.1: #55777.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.1: #55778.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.5: #55779.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #55780.