Confluent Schema Registry

Available in Zilla Plus

Overview

Confluent Schema Registry is a centralized schema management service that enables the storage, retrieval, and evolution of schemas for Kafka data streams. In Zilla, the Confluent Schema Registry serves as a schema catalog, allowing dynamic schema resolution and validation for messages processed within Zilla’s event-driven framework. Key benefits include:

• Dynamic Schema Resolution: Zilla fetches schemas from Confluent Schema Registry at runtime, reducing manual configuration and ensuring schema consistency.
• Enhanced Data Validation: Messages are validated against predefined schemas, improving data integrity and preventing format mismatches.

catalog:
  type: confluent-schema-registry
  options:
    url: http://reg.example.com:8081
    context: default

Configuration (* required)

vault

vault

string

Vault name.

options

options

object

The schema-registry specific options.

Property	Type	Description
options.url	string	Schema Registry URL to access schemas via API calls.
options.context	string	Default: default
options.max-age	integer	Default: 300
options.tls	object	TLS configuration for connecting to secure Schema Registry. A configured vault is required to manage the keys and certificates necessary for TLS authentication.
options.tls.keys	string[]	A list of reference names for the Vault key.
options.tls.trust	string[]	A list of reference names for the Vault certificate.
options.tls.trustcacerts	boolean	Trust CA certificates. When the this property is not explicitly set it will be automatically set to true if options.tls.trust is null.
options.credentials	object	Configures the credentials used to authenticate the user.
options.credentials.headers	object	Authentication headers to be included in requests to the Schema Registry.
options.credentials.headers.authorization	string	The authorization header for authenticating API requests. For example, use a Basic token or Bearer token format.

Examples

TLS configuration examples.

tls:
  trust:
    - serverca
  keys:
    - client1

Credential examples.

credentials:
  headers:
    authorization: Basic dXNlcjpzZWNyZXQ=