It supports plaintext and SCRAM-SHA authentication, as well as optional TLS configuration.
Schema
A comma-separated list of Kafka broker addresses in the form
Example:
host:port.Example:
"b-1.example.com:9092,b-2.example.com:9092"Kafka topic to subscribe to.
Consumer group ID for this Tangent node.
Defaults to
Defaults to
tangent-node.Kafka security protocol to use.
Defaults to
Typical values:
Defaults to
PLAINTEXT.Typical values:
PLAINTEXT, SASL_SSL, SSL.Path to CA certificate file if using SSL/TLS.
Path to the client certificate file if required by your MSK cluster.
Path to the client private key file if required by your MSK cluster.
Specifies how incoming Kafka message payloads are decoded before being sent to your plugin.
See Decoding Options for details.
See Decoding Options for details.
auth
Authentication settings for connecting to MSK.
Authentication mode.
Currently only
Currently only
scram is supported.SASL mechanism to use for SCRAM authentication.
Defaults to
Defaults to
SCRAM-SHA-512.Username for SASL authentication.
Password for SASL authentication.
This is stored securely using
This is stored securely using
SecretString.Example
tangent.yaml
🧠 Notes
- Tangent uses Kafka’s standard consumer group semantics.
- If
auth.modeis set toscram, ensure the brokers support SASL/SCRAM. - TLS parameters are optional but recommended in production.
- The
decodingfield determines how message bytes are parsed (e.g.json,ndjson,raw).