How to Configure secret-key-path for DM-master After Version v8.0.0

This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: v8.0.0版本后DM-master 如何配置 secret-key-path

| username: 宸凡_22

【TiDB Usage Environment】Production Environment / Testing / PoC
【TiDB Version】
【Reproduction Path】What operations were performed when the issue occurred
【Encountered Issue: Issue Phenomenon and Impact】
【Resource Configuration】Go to TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
【Attachments: Screenshots / Logs / Monitoring】

| username: TiDBer_QYr0vohO | Original post link

secret-key-path: The path where the key used to encrypt and decrypt the upstream and downstream passwords is located. The content of this file must be a 64-character hexadecimal AES-256 key.

| username: 宸凡_22 | Original post link

This is the official documentation. I added this parameter to the configuration file, but after restarting the service, it reported that there was no such parameter: parse cmd flags err: master config contained unknown configuration options: secret-key-path.

| username: zhaokede | Original post link

I haven’t used such a high version before, I’ll mark it down for future learning.

| username: yytest | Original post link

Refer to the official documentation.

| username: h5n1 | Original post link

The sample provided in the official documentation is inconsistent with the config file. Use tiup dm edit-config to configure each master server as follows:

The key file is a 64-character hexadecimal string.