Open joelbixbyrevel opened 9 months ago
Not seeing any clear workarounds for this one. I could see this being solved by moving configuration to the secrets template. Otherwise maybe some coordination required between fleet-telemtery codebase to support credentials outside of this configuration.
Issue
For those using SASL authentication Kafka, current configuration file may contain authentication secrets.
Expectation
SASL credentials have a place in secure storage.