br: migrate restore checkpoint data to the downstream cluster temporary database

[Leavrth]

What problem does this PR solve?

Issue Number: close #55870

Problem Summary:
BR restore should not have the permission to write/delete the external storage.

What changed and how does it work?

migrate restore checkpoint data to the downstream cluster temporary database

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.

None

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from leavrth, ensuring that each of them provides their approval before proceeding. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• br/OWNERS

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

[tiprow]

Hi @Leavrth. 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

Attention: Patch coverage is 26.86869% with 362 lines in your changes missing coverage. Please review.

Project coverage is 74.0764%. Comparing base (027f01b) to head (681bb25).
Report is 17 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #56075        +/-   ##
================================================
+ Coverage   72.8742%   74.0764%   +1.2021%     
================================================
  Files          1604       1622        +18     
  Lines        446838     451859      +5021     
================================================
+ Hits         325630     334721      +9091     
+ Misses       101150      96711      -4439     
- Partials      20058      20427       +369     

Flag	Coverage Δ
integration	45.7602% <26.8686%> (?)

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

Components	Coverage Δ
dumpling	52.9567% <ø> (ø)
parser	∅ <ø> (∅)
br	55.7098% <26.8686%> (+10.0795%)	⬆️

[ti-chi-bot]

@Leavrth: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
idc-jenkins-ci-tidb/build	681bb25	link	true	/test build
idc-jenkins-ci-tidb/unit-test	681bb25	link	true	/test unit-test
idc-jenkins-ci-tidb/check_dev_2	681bb25	link	true	/test check-dev2
idc-jenkins-ci-tidb/mysql-test	681bb25	link	true	/test mysql-test
pull-br-integration-test	681bb25	link	true	/test pull-br-integration-test

Full PR test history. Your PR dashboard.

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/test-infra repository. I understand the commands that are listed here.