Confluent
This page describes connecting Lenses to Confluent schema registries.
Only one Schema Registry connection is allowed.
Name must be schema-registry.
See JSON schema for support.
Environment variables are supported; escape the dollar sign
sslKeystorePassword:
value: "\${ENV_VAR_NAME}"Simple configuration, with JMX metrics
The URLs (nodes) should always have a scheme defined (http:// or https://).
confluentSchemaRegistry:
- name: schema-registry
tags: ["tag1"]
version: 1
configuration:
schemaRegistryUrls:
value:
- http://my-sr.host1:8081
- http://my-sr.host2:8081
## all metrics properties are optional
metricsPort:
value: 9581
metricsType:
value: JMX
metricsSsl:
value: falseBasic authentication
For Basic Authentication, define username and password properties.
TLS with custom truststore
A custom truststore is needed when the Schema Registry is served over TLS (encryption-in-transit) and the Registry’s certificate is not signed by a trusted CA.
TLS with client authentication
A custom truststore might be necessary too (see above).
Hard or soft delete
By default, Lenses will use hard delete for Schema Registry. To use soft delete, add the following property:
Last updated
Was this helpful?

