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
Redpanda version: v22.1.3 (rev d1a4e00)
rpk redpanda start strips out empty TLS config from redpanda.yaml.
rpk redpanda start
running it with a config like
rpk: tls: truststore_file: "" cert_file: "" key_file: "" enable_usage_stats: true
will change to
rpk: enable_usage_stats: true
If all fields are empty then it should leave the property empty instead of stripping it out:
rpk: tls: {}
rpk: tls: truststore_file: "" cert_file: "" key_file: ""
You can do this also using a container.
This is happening all the time when building the docker image since it takes the sample config file in https://github.com/redpanda-data/redpanda/blob/dev/conf/redpanda.yaml
The text was updated successfully, but these errors were encountered:
r-vasquez
Successfully merging a pull request may close this issue.
Version & Environment
Redpanda version: v22.1.3 (rev d1a4e00)
What went wrong?
rpk redpanda start
strips out empty TLS config from redpanda.yaml.running it with a config like
will change to
What should have happened instead?
If all fields are empty then it should leave the property empty instead of stripping it out:
How to reproduce the issue?
rpk redpanda start
a. This will change your config file and strip out TLS
You can do this also using a container.
Additional information
This is happening all the time when building the docker image since it takes the sample config file in https://github.com/redpanda-data/redpanda/blob/dev/conf/redpanda.yaml
The text was updated successfully, but these errors were encountered: