UCP: Support both encrypted and unencrypted passwords for the upstream and downstream database

[csuzhangxc]

Feature Request

Is your feature request related to a problem? Please describe:

Both encrypted and unencrypted passwords (by dmctl) are supported.

Describe the feature you'd like:

Support to pass both encrypted and unencrypted passwords (by dmctl) for the upstream and downstream database.

Score

600

Mentor(s)

• @csuzhangxc

Contact the mentors: #tidb-challenge-program channel in TiDB Community Slack Workspace

Recommended Skills

• Golang
• Experience with DM

Learning Materials

• DM source reading
• DM document

[Kuri-su]

/pick-up-challenge

[sre-bot]

@Kuri-su pick up issue success

[Kuri-su]

Do i need to support like this?

$ dmctl --decrypt xxxxxxxxxxxxxxxxxxxxxxxxxxx
mypassword

but i don't know what's mean about "for the upstream and downstream database" in title 😂

[csuzhangxc]

Do i need to support like this?

$ dmctl --decrypt xxxxxxxxxxxxxxxxxxxxxxxxxxx
mypassword

but i don't know what's mean about "for the upstream and downstream database" in title 😂

@Kuri-su I mean, both encrypted or plaintext passwords are accepted in source.toml and task.yaml.

"upstream database" means passwords for the upstream/source MySQL instances, and "downstream database" means passwords for the downstream/target TiDB.

[Kuri-su]

Do i need to support like this?

$ dmctl --decrypt xxxxxxxxxxxxxxxxxxxxxxxxxxx
mypassword

but i don't know what's mean about "for the upstream and downstream database" in title joy

@Kuri-su I mean, both encrypted or plaintext passwords are accepted in source.toml and task.yaml.

"upstream database" means passwords for the upstream/source MySQL instances, and "downstream database" means passwords for the downstream/target TiDB.

ok, i got it.