Skip to content

Log Backup Leak GCS Credential #60209

@apollodafoni

Description

@apollodafoni

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

  • do log backup on GCP cluster
  • use GCS credential file for permissions

2. What did you expect to see? (Required)

no GCS credential leak

3. What did you see instead (Required)

When using the GCS credential file, the credentials were exposed when adding the log backup task.

2025/03/10 13:49:28.778 +00:00] [INFO] [advancer.go:436] ["added event"] [task="storage:<gcs:<bucket:"pinterest-compaction-test" prefix:"logbackup" CredentialsBlob:"[REDACTED]"type\": \"service_account\",\n \"project_id\": \"qa-infra-dev\",\n \"private_key_id\": \"xxxxx\",\n \"private_key\": \"-----BEGIN PRIVATE KEY-----\\

4. What is your TiDB version? (Required)

9.0.0-master

Metadata

Metadata

Assignees

Labels

affects-6.5This bug affects the 6.5.x(LTS) versions.affects-7.1This bug affects the 7.1.x(LTS) versions.affects-7.5This bug affects the 7.5.x(LTS) versions.affects-8.1This bug affects the 8.1.x(LTS) versions.affects-8.5This bug affects the 8.5.x(LTS) versions.component/brThis issue is related to BR of TiDB.severity/majortype/bugThe issue is confirmed as a bug.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions