We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
--etcd-password
Meta prints the following log when I started it with etcd. I think we should hide it when printing to the log.
2023-10-23T08:51:54.600602553Z INFO risingwave_cmd_all::standalone: starting meta-node thread with cli args: ["meta-node", "--listen-addr", "127.0.0.1:5690", "--advertise-addr", "127.0.0.1:5690", "--dashboard-host", "0.0.0.0:5691", "--prometheus-host", "0.0.0.0:1250", "--state-store", "hummock+memory", "--data-directory", "hummock", "--config-path", "/risingwave/config/risingwave.toml", "--backend", "etcd", "--etcd-endpoints", "etcd.default.svc:2379", "--etcd-auth", "--etcd-username", "root", "--etcd-password", "q2mqOcMrjU"]
Hide the values with *, for example, or else omit it.
*
"meta-node", "--listen-addr", "127.0.0.1:5690", "--advertise-addr", "127.0.0.1:5690", "--dashboard-host", "0.0.0.0:5691", "--prometheus-host", "0.0.0.0:1250", "--state-store", "hummock+memory", "--data-directory", "hummock", "--config-path", "/risingwave/config/risingwave.toml", "--backend", "etcd", "--etcd-endpoints", "etcd.default.svc:2379", "--etcd-auth", "--etcd-username", "root", "--etcd-password", "********"
No response
The text was updated successfully, but these errors were encountered:
related: #12673
Sorry, something went wrong.
kwannoel
Successfully merging a pull request may close this issue.
Is your feature request related to a problem? Please describe.
Meta prints the following log when I started it with etcd. I think we should hide it when printing to the log.
Describe the solution you'd like
Hide the values with
*
, for example, or else omit it.Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: