This is an automated email from the ASF dual-hosted git repository.
oscerd pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-kamelets.git
The following commit(s) were added to refs/heads/main by this push:
new affc5f1c4 chore: deprecate the seven Apicurio Registry Kafka Kamelets
(#3144) (#3184)
affc5f1c4 is described below
commit affc5f1c48b87f74f857132bcb65b4d7c0c19d50
Author: Claus Ibsen <[email protected]>
AuthorDate: Wed Nov 18 09:59:13 2026 +0100
chore: deprecate the seven Apicurio Registry Kafka Kamelets (#3144) (#3184)
kafka-apicurio-registry-not-secured-sink/-source,
kafka-batch-apicurio-registry-not-secured-source,
kafka-batch-apicurio-registry-source,
kafka-not-secured-apicurio-registry-json-source/-sink/-source get the
support
level Deprecated, a description that says they will be removed in a later
release, and a note on their doc pages. Schema registry support is planned
as an option of the Kafka Kamelets instead (#3182, #3183).
Co-authored-by: Claude Opus 5.5 <[email protected]>
---
...urio-registry-not-secured-sink-description.adoc | 3 ++
...io-registry-not-secured-source-description.adoc | 3 ++
...io-registry-not-secured-source-description.adoc | 3 ++
...batch-apicurio-registry-source-description.adoc | 3 ++
...-apicurio-registry-json-source-description.adoc | 3 ++
...secured-apicurio-registry-sink-description.adoc | 3 ++
...cured-apicurio-registry-source-description.adoc | 3 ++
...apicurio-registry-not-secured-sink.kamelet.yaml | 6 ++--
...icurio-registry-not-secured-source.kamelet.yaml | 6 ++--
...icurio-registry-not-secured-source.kamelet.yaml | 6 ++--
...fka-batch-apicurio-registry-source.kamelet.yaml | 6 ++--
...ured-apicurio-registry-json-source.kamelet.yaml | 6 ++--
...not-secured-apicurio-registry-sink.kamelet.yaml | 6 ++--
...t-secured-apicurio-registry-source.kamelet.yaml | 6 ++--
.../main/resources/META-INF/kamelets-index.json | 42 +++++++++++-----------
...apicurio-registry-not-secured-sink.kamelet.yaml | 6 ++--
...icurio-registry-not-secured-source.kamelet.yaml | 6 ++--
...icurio-registry-not-secured-source.kamelet.yaml | 6 ++--
...fka-batch-apicurio-registry-source.kamelet.yaml | 6 ++--
...ured-apicurio-registry-json-source.kamelet.yaml | 6 ++--
...not-secured-apicurio-registry-sink.kamelet.yaml | 6 ++--
...t-secured-apicurio-registry-source.kamelet.yaml | 6 ++--
22 files changed, 84 insertions(+), 63 deletions(-)
diff --git
a/docs/modules/ROOT/partials/kafka-apicurio-registry-not-secured-sink-description.adoc
b/docs/modules/ROOT/partials/kafka-apicurio-registry-not-secured-sink-description.adoc
index 01dd72fe4..a4bebceff 100644
---
a/docs/modules/ROOT/partials/kafka-apicurio-registry-not-secured-sink-description.adoc
+++
b/docs/modules/ROOT/partials/kafka-apicurio-registry-not-secured-sink-description.adoc
@@ -1,5 +1,8 @@
== Kafka Not Secured with Apicurio Registry Sink Kamelet Description
+NOTE: This Kamelet is deprecated and will be removed in a later release, as
the Kafka Kamelets are reduced to a
+few.
+
=== Schema Registry Integration
This Kamelet integrates with Apicurio Registry for schema management and
serialization of Avro data. The registry provides centralized schema storage
and versioning capabilities.
diff --git
a/docs/modules/ROOT/partials/kafka-apicurio-registry-not-secured-source-description.adoc
b/docs/modules/ROOT/partials/kafka-apicurio-registry-not-secured-source-description.adoc
index e542080a6..5ca344589 100644
---
a/docs/modules/ROOT/partials/kafka-apicurio-registry-not-secured-source-description.adoc
+++
b/docs/modules/ROOT/partials/kafka-apicurio-registry-not-secured-source-description.adoc
@@ -1,5 +1,8 @@
== Kafka Apicurio Registry Not Secured Source Kamelet Description
+NOTE: This Kamelet is deprecated and will be removed in a later release, as
the Kafka Kamelets are reduced to a
+few.
+
=== Authentication methods
This Kamelet connects to Kafka using:
diff --git
a/docs/modules/ROOT/partials/kafka-batch-apicurio-registry-not-secured-source-description.adoc
b/docs/modules/ROOT/partials/kafka-batch-apicurio-registry-not-secured-source-description.adoc
index b94920537..beb5c203b 100644
---
a/docs/modules/ROOT/partials/kafka-batch-apicurio-registry-not-secured-source-description.adoc
+++
b/docs/modules/ROOT/partials/kafka-batch-apicurio-registry-not-secured-source-description.adoc
@@ -1,5 +1,8 @@
== Kafka Batch Apicurio Registry Not Secured Source Kamelet Description
+NOTE: This Kamelet is deprecated and will be removed in a later release, as
the Kafka Kamelets are reduced to a
+few.
+
=== Authentication methods
This Kamelet connects to Kafka using:
diff --git
a/docs/modules/ROOT/partials/kafka-batch-apicurio-registry-source-description.adoc
b/docs/modules/ROOT/partials/kafka-batch-apicurio-registry-source-description.adoc
index be7dd4fa6..de360bb31 100644
---
a/docs/modules/ROOT/partials/kafka-batch-apicurio-registry-source-description.adoc
+++
b/docs/modules/ROOT/partials/kafka-batch-apicurio-registry-source-description.adoc
@@ -1,5 +1,8 @@
== Kafka Batch Apicurio Registry Source Kamelet Description
+NOTE: This Kamelet is deprecated and will be removed in a later release, as
the Kafka Kamelets are reduced to a
+few.
+
=== Authentication methods
This Kamelet connects to Kafka using:
diff --git
a/docs/modules/ROOT/partials/kafka-not-secured-apicurio-registry-json-source-description.adoc
b/docs/modules/ROOT/partials/kafka-not-secured-apicurio-registry-json-source-description.adoc
index 644e180c2..d0f533b2d 100644
---
a/docs/modules/ROOT/partials/kafka-not-secured-apicurio-registry-json-source-description.adoc
+++
b/docs/modules/ROOT/partials/kafka-not-secured-apicurio-registry-json-source-description.adoc
@@ -1,5 +1,8 @@
== Kafka-not-secured-apicurio-registry-json-source Kamelet Description
+NOTE: This Kamelet is deprecated and will be removed in a later release, as
the Kafka Kamelets are reduced to a
+few.
+
=== Authentication methods
This Kamelet connects to Kafka with no login and no TLS. It logs in to the
Apicurio Registry
diff --git
a/docs/modules/ROOT/partials/kafka-not-secured-apicurio-registry-sink-description.adoc
b/docs/modules/ROOT/partials/kafka-not-secured-apicurio-registry-sink-description.adoc
index 14f6454f6..50e01211c 100644
---
a/docs/modules/ROOT/partials/kafka-not-secured-apicurio-registry-sink-description.adoc
+++
b/docs/modules/ROOT/partials/kafka-not-secured-apicurio-registry-sink-description.adoc
@@ -1,5 +1,8 @@
== Kafka Not Secured with Apicurio Registry secured with Keycloak Sink Kamelet
Description
+NOTE: This Kamelet is deprecated and will be removed in a later release, as
the Kafka Kamelets are reduced to a
+few.
+
=== Schema Registry Security
This Kamelet integrates with Apicurio Registry that is secured with Keycloak
authentication. While the Kafka broker connection is not secured, the schema
registry access requires proper authentication.
diff --git
a/docs/modules/ROOT/partials/kafka-not-secured-apicurio-registry-source-description.adoc
b/docs/modules/ROOT/partials/kafka-not-secured-apicurio-registry-source-description.adoc
index c650ec6e3..51470d965 100644
---
a/docs/modules/ROOT/partials/kafka-not-secured-apicurio-registry-source-description.adoc
+++
b/docs/modules/ROOT/partials/kafka-not-secured-apicurio-registry-source-description.adoc
@@ -1,5 +1,8 @@
== Kafka-not-secured-apicurio-registry-source Kamelet Description
+NOTE: This Kamelet is deprecated and will be removed in a later release, as
the Kafka Kamelets are reduced to a
+few.
+
=== Authentication methods
This Kamelet connects to Kafka with no login and no TLS. It logs in to the
Apicurio Registry
diff --git a/kamelets/kafka-apicurio-registry-not-secured-sink.kamelet.yaml
b/kamelets/kafka-apicurio-registry-not-secured-sink.kamelet.yaml
index f89050f78..ef6642bf7 100644
--- a/kamelets/kafka-apicurio-registry-not-secured-sink.kamelet.yaml
+++ b/kamelets/kafka-apicurio-registry-not-secured-sink.kamelet.yaml
@@ -19,7 +19,7 @@ kind: Kamelet
metadata:
name: kafka-apicurio-registry-not-secured-sink
annotations:
- camel.apache.org/kamelet.support.level: "Stable"
+ camel.apache.org/kamelet.support.level: "Deprecated"
camel.apache.org/catalog.version: "4.24.0-SNAPSHOT"
camel.apache.org/kamelet.icon:
"data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4NCjwhLS0gR2VuZXJhdG9yOiBBZG9iZSBJbGx1c3RyYXRvciAxOS4wLjAsIFNWRyBFeHBvcnQgUGx1Zy1JbiAuIFNWRyBWZXJzaW9uOiA2LjAwIEJ1aWxkIDApICAtLT4NCjxzdmcgdmVyc2lvbj0iMS4xIiBpZD0iTGF5ZXJfMSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB4bWxuczp4bGluaz0iaHR0cDovL3d3dy53My5vcmcvMTk5OS94bGluayIgeD0iMHB4IiB5PSIwcHgiDQoJIHZpZXdCb3g9IjAgMCA1MDAgNTAwIiBzdHlsZT0iZW5hYmxlLWJhY2tncm91bmQ6bmV3IDAgMCA1MD
[...]
camel.apache.org/provider: "Apache Software Foundation"
@@ -31,9 +31,9 @@ spec:
definition:
title: "Kafka Not Secured with Apicurio Registry Sink"
description: |-
- Sends each message as an Avro record to a topic in Apache Kafka, with
the schema kept in an Apicurio Registry, and no login or TLS to either.
+ Deprecated, to be removed in a later release: sends each message as an
Avro record to a topic in Apache Kafka, with the schema kept in an Apicurio
Registry, and no login or TLS to either.
- Use it to publish records that other applications read with the schema
of the registry, on a Kafka and a registry that need no login, such as in
development. When the registry is secured with Keycloak use
`kafka-not-secured-apicurio-registry-sink`; for records without a schema use
`kafka-sink`.
+ Use it to publish records that other applications read with the schema
of the registry, on a Kafka and a registry that need no login, such as in
development. When the registry is secured with Keycloak use
`kafka-not-secured-apicurio-registry-sink`; for records without a schema use
`kafka-sink`. This Kamelet is deprecated and will be removed in a later
release, as the Kafka Kamelets are reduced to a few.
Input: the body must be an Avro object, such as an Avro `GenericRecord`
or an object of a class generated from the schema; it is written as Avro
binary. A body of text is written as an Avro string, and so fails unless the
schema is a string. The optional `key` header (or `ce-key`) becomes the key of
the record, and the optional `partition-key` header (or `ce-partitionkey`) is
the number of the partition to write to. The other headers of the message,
except the Camel ones, are sent [...]
diff --git a/kamelets/kafka-apicurio-registry-not-secured-source.kamelet.yaml
b/kamelets/kafka-apicurio-registry-not-secured-source.kamelet.yaml
index c6bc40a65..cd1c7c48d 100644
--- a/kamelets/kafka-apicurio-registry-not-secured-source.kamelet.yaml
+++ b/kamelets/kafka-apicurio-registry-not-secured-source.kamelet.yaml
@@ -19,7 +19,7 @@ kind: Kamelet
metadata:
name: kafka-apicurio-registry-not-secured-source
annotations:
- camel.apache.org/kamelet.support.level: "Preview"
+ camel.apache.org/kamelet.support.level: "Deprecated"
camel.apache.org/catalog.version: "4.24.0-SNAPSHOT"
camel.apache.org/kamelet.icon:
"data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4NCjwhLS0gR2VuZXJhdG9yOiBBZG9iZSBJbGx1c3RyYXRvciAxOS4wLjAsIFNWRyBFeHBvcnQgUGx1Zy1JbiAuIFNWRyBWZXJzaW9uOiA2LjAwIEJ1aWxkIDApICAtLT4NCjxzdmcgdmVyc2lvbj0iMS4xIiBpZD0iTGF5ZXJfMSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB4bWxuczp4bGluaz0iaHR0cDovL3d3dy53My5vcmcvMTk5OS94bGluayIgeD0iMHB4IiB5PSIwcHgiDQoJIHZpZXdCb3g9IjAgMCA1MDAgNTAwIiBzdHlsZT0iZW5hYmxlLWJhY2tncm91bmQ6bmV3IDAgMCA1MD
[...]
camel.apache.org/provider: "Apache Software Foundation"
@@ -31,9 +31,9 @@ spec:
definition:
title: "Kafka Not Secured with Apicurio Registry Source"
description: |-
- Receives each record written with a JSON Schema from topics in Apache
Kafka, with the schema kept in an Apicurio Registry, and no login or TLS to
either.
+ Deprecated, to be removed in a later release: receives each record
written with a JSON Schema from topics in Apache Kafka, with the schema kept in
an Apicurio Registry, and no login or TLS to either.
- Use it to read JSON records that other applications write with a JSON
Schema of the registry, on a Kafka and a registry that need no login, such as
in development. For Avro records use
`kafka-batch-apicurio-registry-not-secured-source`; when the registry is
secured with Keycloak use `kafka-not-secured-apicurio-registry-json-source`;
for records without a schema use `kafka-source`.
+ Use it to read JSON records that other applications write with a JSON
Schema of the registry, on a Kafka and a registry that need no login, such as
in development. For Avro records use
`kafka-batch-apicurio-registry-not-secured-source`; when the registry is
secured with Keycloak use `kafka-not-secured-apicurio-registry-json-source`;
for records without a schema use `kafka-source`. This Kamelet is deprecated and
will be removed in a later release, as the Kafka Kamelets are reduced t [...]
Output: the body is the value of the record as parsed JSON. The
`kafka-topic`, `kafka-key`, `kafka-partition`, `kafka-offset` and
`kafka-timestamp` (in milliseconds since 1970) headers say where the record
came from. They are also set as `ce-kafkatopic`, `ce-kafkakey` and so on, and
as the `CamelKafka*` headers that the Kafka actions read. The record headers
become message headers, as text unless `deserializeHeaders` is false.
diff --git
a/kamelets/kafka-batch-apicurio-registry-not-secured-source.kamelet.yaml
b/kamelets/kafka-batch-apicurio-registry-not-secured-source.kamelet.yaml
index 29e175114..9d3bb0a5a 100644
--- a/kamelets/kafka-batch-apicurio-registry-not-secured-source.kamelet.yaml
+++ b/kamelets/kafka-batch-apicurio-registry-not-secured-source.kamelet.yaml
@@ -19,7 +19,7 @@ kind: Kamelet
metadata:
name: kafka-batch-apicurio-registry-not-secured-source
annotations:
- camel.apache.org/kamelet.support.level: "Preview"
+ camel.apache.org/kamelet.support.level: "Deprecated"
camel.apache.org/catalog.version: "4.24.0-SNAPSHOT"
camel.apache.org/kamelet.icon:
"data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4NCjwhLS0gR2VuZXJhdG9yOiBBZG9iZSBJbGx1c3RyYXRvciAxOS4wLjAsIFNWRyBFeHBvcnQgUGx1Zy1JbiAuIFNWRyBWZXJzaW9uOiA2LjAwIEJ1aWxkIDApICAtLT4NCjxzdmcgdmVyc2lvbj0iMS4xIiBpZD0iTGF5ZXJfMSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB4bWxuczp4bGluaz0iaHR0cDovL3d3dy53My5vcmcvMTk5OS94bGluayIgeD0iMHB4IiB5PSIwcHgiDQoJIHZpZXdCb3g9IjAgMCA1MDAgNTAwIiBzdHlsZT0iZW5hYmxlLWJhY2tncm91bmQ6bmV3IDAgMCA1MD
[...]
camel.apache.org/provider: "Apache Software Foundation"
@@ -31,9 +31,9 @@ spec:
definition:
title: "Kafka Batch Not Secured with Apicurio Registry Source"
description: |-
- Receives Avro records from topics in Apache Kafka in batches, with the
schema kept in an Apicurio Registry, and no login or TLS to either.
+ Deprecated, to be removed in a later release: receives Avro records from
topics in Apache Kafka in batches, with the schema kept in an Apicurio
Registry, and no login or TLS to either.
- Use it to read many Avro records at once, as written by
`kafka-apicurio-registry-not-secured-sink`, on a Kafka and a registry that need
no login, such as in development. When the registry is secured with Keycloak
use `kafka-batch-apicurio-registry-source`.
+ Use it to read many Avro records at once, as written by
`kafka-apicurio-registry-not-secured-sink`, on a Kafka and a registry that need
no login, such as in development. When the registry is secured with Keycloak
use `kafka-batch-apicurio-registry-source`. This Kamelet is deprecated and will
be removed in a later release, as the Kafka Kamelets are reduced to a few.
Output: the body is a List with one entry per record, up to `batchSize`.
Each entry is a message of its own, with the value of the record as its body
(an Avro `GenericRecord`, whose text form is JSON), and the key, offset and
timestamp of the record in its `CamelKafkaKey`, `CamelKafkaOffset` and
`CamelKafkaTimestamp` headers. The record headers are in the entries too, as
bytes. The message itself has the `CamelKafkaTopic` and `CamelKafkaPartition`
headers. The `kafka-topic`, `kafka [...]
diff --git a/kamelets/kafka-batch-apicurio-registry-source.kamelet.yaml
b/kamelets/kafka-batch-apicurio-registry-source.kamelet.yaml
index f6578e55a..b96815125 100644
--- a/kamelets/kafka-batch-apicurio-registry-source.kamelet.yaml
+++ b/kamelets/kafka-batch-apicurio-registry-source.kamelet.yaml
@@ -19,7 +19,7 @@ kind: Kamelet
metadata:
name: kafka-batch-apicurio-registry-source
annotations:
- camel.apache.org/kamelet.support.level: "Preview"
+ camel.apache.org/kamelet.support.level: "Deprecated"
camel.apache.org/catalog.version: "4.24.0-SNAPSHOT"
camel.apache.org/kamelet.icon:
"data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4NCjwhLS0gR2VuZXJhdG9yOiBBZG9iZSBJbGx1c3RyYXRvciAxOS4wLjAsIFNWRyBFeHBvcnQgUGx1Zy1JbiAuIFNWRyBWZXJzaW9uOiA2LjAwIEJ1aWxkIDApICAtLT4NCjxzdmcgdmVyc2lvbj0iMS4xIiBpZD0iTGF5ZXJfMSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB4bWxuczp4bGluaz0iaHR0cDovL3d3dy53My5vcmcvMTk5OS94bGluayIgeD0iMHB4IiB5PSIwcHgiDQoJIHZpZXdCb3g9IjAgMCA1MDAgNTAwIiBzdHlsZT0iZW5hYmxlLWJhY2tncm91bmQ6bmV3IDAgMCA1MD
[...]
camel.apache.org/provider: "Apache Software Foundation"
@@ -31,9 +31,9 @@ spec:
definition:
title: "Kafka Batch with Apicurio Registry secured with Keycloak Source"
description: |-
- Receives Avro records from topics in Apache Kafka in batches, with the
schema kept in an Apicurio Registry secured with Keycloak.
+ Deprecated, to be removed in a later release: receives Avro records from
topics in Apache Kafka in batches, with the schema kept in an Apicurio Registry
secured with Keycloak.
- Use it to read many Avro records at once, when the registry needs a
Keycloak login and Kafka needs none. For one record at a time use
`kafka-not-secured-apicurio-registry-source`; when the registry needs no login
use `kafka-batch-apicurio-registry-not-secured-source`.
+ Use it to read many Avro records at once, when the registry needs a
Keycloak login and Kafka needs none. For one record at a time use
`kafka-not-secured-apicurio-registry-source`; when the registry needs no login
use `kafka-batch-apicurio-registry-not-secured-source`. This Kamelet is
deprecated and will be removed in a later release, as the Kafka Kamelets are
reduced to a few.
Output: the body is a List with one entry per record, up to `batchSize`.
Each entry is a message of its own, with the value of the record as its body
(an Avro `GenericRecord`, whose text form is JSON), and the key, offset and
timestamp of the record in its `CamelKafkaKey`, `CamelKafkaOffset` and
`CamelKafkaTimestamp` headers. The record headers are in the entries too, as
bytes. The message itself has the `CamelKafkaTopic` and `CamelKafkaPartition`
headers. The `kafka-topic`, `kafka [...]
diff --git
a/kamelets/kafka-not-secured-apicurio-registry-json-source.kamelet.yaml
b/kamelets/kafka-not-secured-apicurio-registry-json-source.kamelet.yaml
index 5ee2f1da6..ef5426e4e 100644
--- a/kamelets/kafka-not-secured-apicurio-registry-json-source.kamelet.yaml
+++ b/kamelets/kafka-not-secured-apicurio-registry-json-source.kamelet.yaml
@@ -19,7 +19,7 @@ kind: Kamelet
metadata:
name: kafka-not-secured-apicurio-registry-json-source
annotations:
- camel.apache.org/kamelet.support.level: "Preview"
+ camel.apache.org/kamelet.support.level: "Deprecated"
camel.apache.org/catalog.version: "4.24.0-SNAPSHOT"
camel.apache.org/kamelet.icon:
"data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4NCjwhLS0gR2VuZXJhdG9yOiBBZG9iZSBJbGx1c3RyYXRvciAxOS4wLjAsIFNWRyBFeHBvcnQgUGx1Zy1JbiAuIFNWRyBWZXJzaW9uOiA2LjAwIEJ1aWxkIDApICAtLT4NCjxzdmcgdmVyc2lvbj0iMS4xIiBpZD0iTGF5ZXJfMSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB4bWxuczp4bGluaz0iaHR0cDovL3d3dy53My5vcmcvMTk5OS94bGluayIgeD0iMHB4IiB5PSIwcHgiDQoJIHZpZXdCb3g9IjAgMCA1MDAgNTAwIiBzdHlsZT0iZW5hYmxlLWJhY2tncm91bmQ6bmV3IDAgMCA1MD
[...]
camel.apache.org/provider: "Apache Software Foundation"
@@ -31,9 +31,9 @@ spec:
definition:
title: "Kafka not secured with Apicurio Registry secured with Keycloak for
JSON schema support Source"
description: |-
- Receives each record written with a JSON Schema from topics in Apache
Kafka, with the schema kept in an Apicurio Registry secured with Keycloak.
+ Deprecated, to be removed in a later release: receives each record
written with a JSON Schema from topics in Apache Kafka, with the schema kept in
an Apicurio Registry secured with Keycloak.
- Use it to read JSON records that other applications write with a JSON
Schema of the registry, when the registry needs a Keycloak login and Kafka
needs none. For Avro records use `kafka-not-secured-apicurio-registry-source`;
when the registry needs no login use
`kafka-apicurio-registry-not-secured-source`.
+ Use it to read JSON records that other applications write with a JSON
Schema of the registry, when the registry needs a Keycloak login and Kafka
needs none. For Avro records use `kafka-not-secured-apicurio-registry-source`;
when the registry needs no login use
`kafka-apicurio-registry-not-secured-source`. This Kamelet is deprecated and
will be removed in a later release, as the Kafka Kamelets are reduced to a few.
Output: the body is the value of the record as parsed JSON. The
`kafka-topic`, `kafka-key`, `kafka-partition`, `kafka-offset` and
`kafka-timestamp` (in milliseconds since 1970) headers say where the record
came from. They are also set as `ce-kafkatopic`, `ce-kafkakey` and so on, and
as the `CamelKafka*` headers that the Kafka actions read. The record headers
become message headers, as text unless `deserializeHeaders` is false.
diff --git a/kamelets/kafka-not-secured-apicurio-registry-sink.kamelet.yaml
b/kamelets/kafka-not-secured-apicurio-registry-sink.kamelet.yaml
index c9b922b6a..a3cc8ef1c 100644
--- a/kamelets/kafka-not-secured-apicurio-registry-sink.kamelet.yaml
+++ b/kamelets/kafka-not-secured-apicurio-registry-sink.kamelet.yaml
@@ -19,7 +19,7 @@ kind: Kamelet
metadata:
name: kafka-not-secured-apicurio-registry-sink
annotations:
- camel.apache.org/kamelet.support.level: "Stable"
+ camel.apache.org/kamelet.support.level: "Deprecated"
camel.apache.org/catalog.version: "4.24.0-SNAPSHOT"
camel.apache.org/kamelet.icon:
"data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4NCjwhLS0gR2VuZXJhdG9yOiBBZG9iZSBJbGx1c3RyYXRvciAxOS4wLjAsIFNWRyBFeHBvcnQgUGx1Zy1JbiAuIFNWRyBWZXJzaW9uOiA2LjAwIEJ1aWxkIDApICAtLT4NCjxzdmcgdmVyc2lvbj0iMS4xIiBpZD0iTGF5ZXJfMSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB4bWxuczp4bGluaz0iaHR0cDovL3d3dy53My5vcmcvMTk5OS94bGluayIgeD0iMHB4IiB5PSIwcHgiDQoJIHZpZXdCb3g9IjAgMCA1MDAgNTAwIiBzdHlsZT0iZW5hYmxlLWJhY2tncm91bmQ6bmV3IDAgMCA1MD
[...]
camel.apache.org/provider: "Apache Software Foundation"
@@ -31,9 +31,9 @@ spec:
definition:
title: "Kafka Not Secured with Apicurio Registry secured with Keycloak
Sink"
description: |-
- Sends each message as an Avro record to a topic in Apache Kafka, with
the schema kept in an Apicurio Registry secured with Keycloak.
+ Deprecated, to be removed in a later release: sends each message as an
Avro record to a topic in Apache Kafka, with the schema kept in an Apicurio
Registry secured with Keycloak.
- Use it to publish records that other applications read with the schema
of the registry, when the registry needs a Keycloak login and Kafka needs none.
When the registry needs no login use
`kafka-apicurio-registry-not-secured-sink`; for records without a schema use
`kafka-sink`.
+ Use it to publish records that other applications read with the schema
of the registry, when the registry needs a Keycloak login and Kafka needs none.
When the registry needs no login use
`kafka-apicurio-registry-not-secured-sink`; for records without a schema use
`kafka-sink`. This Kamelet is deprecated and will be removed in a later
release, as the Kafka Kamelets are reduced to a few.
Input: the body must be an Avro object, such as an Avro `GenericRecord`
or an object of a class generated from the schema; it is written as Avro
binary. A body of text is written as an Avro string, and so fails unless the
schema is a string. The optional `key` header (or `ce-key`) becomes the key of
the record, and the optional `partition-key` header (or `ce-partitionkey`) is
the number of the partition to write to. The other headers of the message,
except the Camel ones, are sent [...]
diff --git a/kamelets/kafka-not-secured-apicurio-registry-source.kamelet.yaml
b/kamelets/kafka-not-secured-apicurio-registry-source.kamelet.yaml
index 1c24d1d0e..6be88a031 100644
--- a/kamelets/kafka-not-secured-apicurio-registry-source.kamelet.yaml
+++ b/kamelets/kafka-not-secured-apicurio-registry-source.kamelet.yaml
@@ -19,7 +19,7 @@ kind: Kamelet
metadata:
name: kafka-not-secured-apicurio-registry-source
annotations:
- camel.apache.org/kamelet.support.level: "Preview"
+ camel.apache.org/kamelet.support.level: "Deprecated"
camel.apache.org/catalog.version: "4.24.0-SNAPSHOT"
camel.apache.org/kamelet.icon:
"data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4NCjwhLS0gR2VuZXJhdG9yOiBBZG9iZSBJbGx1c3RyYXRvciAxOS4wLjAsIFNWRyBFeHBvcnQgUGx1Zy1JbiAuIFNWRyBWZXJzaW9uOiA2LjAwIEJ1aWxkIDApICAtLT4NCjxzdmcgdmVyc2lvbj0iMS4xIiBpZD0iTGF5ZXJfMSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB4bWxuczp4bGluaz0iaHR0cDovL3d3dy53My5vcmcvMTk5OS94bGluayIgeD0iMHB4IiB5PSIwcHgiDQoJIHZpZXdCb3g9IjAgMCA1MDAgNTAwIiBzdHlsZT0iZW5hYmxlLWJhY2tncm91bmQ6bmV3IDAgMCA1MD
[...]
camel.apache.org/provider: "Apache Software Foundation"
@@ -31,9 +31,9 @@ spec:
definition:
title: "Kafka not secured with Apicurio Registry secured with Keycloak
Source"
description: |-
- Receives each Avro record from topics in Apache Kafka, with the schema
kept in an Apicurio Registry secured with Keycloak.
+ Deprecated, to be removed in a later release: receives each Avro record
from topics in Apache Kafka, with the schema kept in an Apicurio Registry
secured with Keycloak.
- Use it to read Avro records, as written by
`kafka-not-secured-apicurio-registry-sink`, when the registry needs a Keycloak
login and Kafka needs none. For JSON Schema records use
`kafka-not-secured-apicurio-registry-json-source`; for batches use
`kafka-batch-apicurio-registry-source`.
+ Use it to read Avro records, as written by
`kafka-not-secured-apicurio-registry-sink`, when the registry needs a Keycloak
login and Kafka needs none. For JSON Schema records use
`kafka-not-secured-apicurio-registry-json-source`; for batches use
`kafka-batch-apicurio-registry-source`. This Kamelet is deprecated and will be
removed in a later release, as the Kafka Kamelets are reduced to a few.
Output: the body is the value of the record as an Avro `GenericRecord`,
whose text form is JSON. The `kafka-topic`, `kafka-key`, `kafka-partition`,
`kafka-offset` and `kafka-timestamp` (in milliseconds since 1970) headers say
where the record came from. They are also set as `ce-kafkatopic`, `ce-kafkakey`
and so on, and as the `CamelKafka*` headers that the Kafka actions read. The
record headers become message headers, as text unless `deserializeHeaders` is
false.
diff --git
a/library/camel-kamelets/src/main/resources/META-INF/kamelets-index.json
b/library/camel-kamelets/src/main/resources/META-INF/kamelets-index.json
index 259870169..f75ed8abd 100644
--- a/library/camel-kamelets/src/main/resources/META-INF/kamelets-index.json
+++ b/library/camel-kamelets/src/main/resources/META-INF/kamelets-index.json
@@ -1342,40 +1342,40 @@
}, {
"name" : "kafka-apicurio-registry-not-secured-sink",
"type" : "sink",
- "supportLevel" : "Stable",
+ "supportLevel" : "Deprecated",
"title" : "Kafka Not Secured with Apicurio Registry Sink",
- "summary" : "Sends each message as an Avro record to a topic in Apache
Kafka, with the schema kept in an Apicurio Registry, and no login or TLS to
either.",
- "description" : "Sends each message as an Avro record to a topic in Apache
Kafka, with the schema kept in an Apicurio Registry, and no login or TLS to
either.\n\nUse it to publish records that other applications read with the
schema of the registry, on a Kafka and a registry that need no login, such as
in development. When the registry is secured with Keycloak use
`kafka-not-secured-apicurio-registry-sink`; for records without a schema use
`kafka-sink`.\n\nInput: the body must be an [...]
+ "summary" : "Deprecated, to be removed in a later release: sends each
message as an Avro record to a topic in Apache Kafka, with the schema kept in
an Apicurio Registry, and no login or TLS to either.",
+ "description" : "Deprecated, to be removed in a later release: sends each
message as an Avro record to a topic in Apache Kafka, with the schema kept in
an Apicurio Registry, and no login or TLS to either.\n\nUse it to publish
records that other applications read with the schema of the registry, on a
Kafka and a registry that need no login, such as in development. When the
registry is secured with Keycloak use
`kafka-not-secured-apicurio-registry-sink`; for records without a schema us
[...]
"group" : "Kafka",
"namespace" : "Kafka",
"provider" : "Apache Software Foundation"
}, {
"name" : "kafka-apicurio-registry-not-secured-source",
"type" : "source",
- "supportLevel" : "Preview",
+ "supportLevel" : "Deprecated",
"title" : "Kafka Not Secured with Apicurio Registry Source",
- "summary" : "Receives each record written with a JSON Schema from topics
in Apache Kafka, with the schema kept in an Apicurio Registry, and no login or
TLS to either.",
- "description" : "Receives each record written with a JSON Schema from
topics in Apache Kafka, with the schema kept in an Apicurio Registry, and no
login or TLS to either.\n\nUse it to read JSON records that other applications
write with a JSON Schema of the registry, on a Kafka and a registry that need
no login, such as in development. For Avro records use
`kafka-batch-apicurio-registry-not-secured-source`; when the registry is
secured with Keycloak use `kafka-not-secured-apicurio-re [...]
+ "summary" : "Deprecated, to be removed in a later release: receives each
record written with a JSON Schema from topics in Apache Kafka, with the schema
kept in an Apicurio Registry, and no login or TLS to either.",
+ "description" : "Deprecated, to be removed in a later release: receives
each record written with a JSON Schema from topics in Apache Kafka, with the
schema kept in an Apicurio Registry, and no login or TLS to either.\n\nUse it
to read JSON records that other applications write with a JSON Schema of the
registry, on a Kafka and a registry that need no login, such as in development.
For Avro records use `kafka-batch-apicurio-registry-not-secured-source`; when
the registry is secured wi [...]
"group" : "Kafka",
"namespace" : "Kafka",
"provider" : "Apache Software Foundation"
}, {
"name" : "kafka-batch-apicurio-registry-not-secured-source",
"type" : "source",
- "supportLevel" : "Preview",
+ "supportLevel" : "Deprecated",
"title" : "Kafka Batch Not Secured with Apicurio Registry Source",
- "summary" : "Receives Avro records from topics in Apache Kafka in batches,
with the schema kept in an Apicurio Registry, and no login or TLS to either.",
- "description" : "Receives Avro records from topics in Apache Kafka in
batches, with the schema kept in an Apicurio Registry, and no login or TLS to
either.\n\nUse it to read many Avro records at once, as written by
`kafka-apicurio-registry-not-secured-sink`, on a Kafka and a registry that need
no login, such as in development. When the registry is secured with Keycloak
use `kafka-batch-apicurio-registry-source`.\n\nOutput: the body is a List with
one entry per record, up to `batchSiz [...]
+ "summary" : "Deprecated, to be removed in a later release: receives Avro
records from topics in Apache Kafka in batches, with the schema kept in an
Apicurio Registry, and no login or TLS to either.",
+ "description" : "Deprecated, to be removed in a later release: receives
Avro records from topics in Apache Kafka in batches, with the schema kept in an
Apicurio Registry, and no login or TLS to either.\n\nUse it to read many Avro
records at once, as written by `kafka-apicurio-registry-not-secured-sink`, on a
Kafka and a registry that need no login, such as in development. When the
registry is secured with Keycloak use `kafka-batch-apicurio-registry-source`.
This Kamelet is deprecated [...]
"group" : "Kafka",
"namespace" : "Kafka",
"provider" : "Apache Software Foundation"
}, {
"name" : "kafka-batch-apicurio-registry-source",
"type" : "source",
- "supportLevel" : "Preview",
+ "supportLevel" : "Deprecated",
"title" : "Kafka Batch with Apicurio Registry secured with Keycloak
Source",
- "summary" : "Receives Avro records from topics in Apache Kafka in batches,
with the schema kept in an Apicurio Registry secured with Keycloak.",
- "description" : "Receives Avro records from topics in Apache Kafka in
batches, with the schema kept in an Apicurio Registry secured with
Keycloak.\n\nUse it to read many Avro records at once, when the registry needs
a Keycloak login and Kafka needs none. For one record at a time use
`kafka-not-secured-apicurio-registry-source`; when the registry needs no login
use `kafka-batch-apicurio-registry-not-secured-source`.\n\nOutput: the body is
a List with one entry per record, up to `batch [...]
+ "summary" : "Deprecated, to be removed in a later release: receives Avro
records from topics in Apache Kafka in batches, with the schema kept in an
Apicurio Registry secured with Keycloak.",
+ "description" : "Deprecated, to be removed in a later release: receives
Avro records from topics in Apache Kafka in batches, with the schema kept in an
Apicurio Registry secured with Keycloak.\n\nUse it to read many Avro records at
once, when the registry needs a Keycloak login and Kafka needs none. For one
record at a time use `kafka-not-secured-apicurio-registry-source`; when the
registry needs no login use `kafka-batch-apicurio-registry-not-secured-source`.
This Kamelet is depreca [...]
"group" : "Kafka",
"namespace" : "Kafka",
"provider" : "Apache Software Foundation"
@@ -1412,30 +1412,30 @@
}, {
"name" : "kafka-not-secured-apicurio-registry-json-source",
"type" : "source",
- "supportLevel" : "Preview",
+ "supportLevel" : "Deprecated",
"title" : "Kafka not secured with Apicurio Registry secured with Keycloak
for JSON schema support Source",
- "summary" : "Receives each record written with a JSON Schema from topics
in Apache Kafka, with the schema kept in an Apicurio Registry secured with
Keycloak.",
- "description" : "Receives each record written with a JSON Schema from
topics in Apache Kafka, with the schema kept in an Apicurio Registry secured
with Keycloak.\n\nUse it to read JSON records that other applications write
with a JSON Schema of the registry, when the registry needs a Keycloak login
and Kafka needs none. For Avro records use
`kafka-not-secured-apicurio-registry-source`; when the registry needs no login
use `kafka-apicurio-registry-not-secured-source`.\n\nOutput: the b [...]
+ "summary" : "Deprecated, to be removed in a later release: receives each
record written with a JSON Schema from topics in Apache Kafka, with the schema
kept in an Apicurio Registry secured with Keycloak.",
+ "description" : "Deprecated, to be removed in a later release: receives
each record written with a JSON Schema from topics in Apache Kafka, with the
schema kept in an Apicurio Registry secured with Keycloak.\n\nUse it to read
JSON records that other applications write with a JSON Schema of the registry,
when the registry needs a Keycloak login and Kafka needs none. For Avro records
use `kafka-not-secured-apicurio-registry-source`; when the registry needs no
login use `kafka-apicurio- [...]
"group" : "Kafka",
"namespace" : "Kafka",
"provider" : "Apache Software Foundation"
}, {
"name" : "kafka-not-secured-apicurio-registry-sink",
"type" : "sink",
- "supportLevel" : "Stable",
+ "supportLevel" : "Deprecated",
"title" : "Kafka Not Secured with Apicurio Registry secured with Keycloak
Sink",
- "summary" : "Sends each message as an Avro record to a topic in Apache
Kafka, with the schema kept in an Apicurio Registry secured with Keycloak.",
- "description" : "Sends each message as an Avro record to a topic in Apache
Kafka, with the schema kept in an Apicurio Registry secured with
Keycloak.\n\nUse it to publish records that other applications read with the
schema of the registry, when the registry needs a Keycloak login and Kafka
needs none. When the registry needs no login use
`kafka-apicurio-registry-not-secured-sink`; for records without a schema use
`kafka-sink`.\n\nInput: the body must be an Avro object, such as an Av [...]
+ "summary" : "Deprecated, to be removed in a later release: sends each
message as an Avro record to a topic in Apache Kafka, with the schema kept in
an Apicurio Registry secured with Keycloak.",
+ "description" : "Deprecated, to be removed in a later release: sends each
message as an Avro record to a topic in Apache Kafka, with the schema kept in
an Apicurio Registry secured with Keycloak.\n\nUse it to publish records that
other applications read with the schema of the registry, when the registry
needs a Keycloak login and Kafka needs none. When the registry needs no login
use `kafka-apicurio-registry-not-secured-sink`; for records without a schema
use `kafka-sink`. This Kamel [...]
"group" : "Kafka",
"namespace" : "Kafka",
"provider" : "Apache Software Foundation"
}, {
"name" : "kafka-not-secured-apicurio-registry-source",
"type" : "source",
- "supportLevel" : "Preview",
+ "supportLevel" : "Deprecated",
"title" : "Kafka not secured with Apicurio Registry secured with Keycloak
Source",
- "summary" : "Receives each Avro record from topics in Apache Kafka, with
the schema kept in an Apicurio Registry secured with Keycloak.",
- "description" : "Receives each Avro record from topics in Apache Kafka,
with the schema kept in an Apicurio Registry secured with Keycloak.\n\nUse it
to read Avro records, as written by `kafka-not-secured-apicurio-registry-sink`,
when the registry needs a Keycloak login and Kafka needs none. For JSON Schema
records use `kafka-not-secured-apicurio-registry-json-source`; for batches use
`kafka-batch-apicurio-registry-source`.\n\nOutput: the body is the value of the
record as an Avro `G [...]
+ "summary" : "Deprecated, to be removed in a later release: receives each
Avro record from topics in Apache Kafka, with the schema kept in an Apicurio
Registry secured with Keycloak.",
+ "description" : "Deprecated, to be removed in a later release: receives
each Avro record from topics in Apache Kafka, with the schema kept in an
Apicurio Registry secured with Keycloak.\n\nUse it to read Avro records, as
written by `kafka-not-secured-apicurio-registry-sink`, when the registry needs
a Keycloak login and Kafka needs none. For JSON Schema records use
`kafka-not-secured-apicurio-registry-json-source`; for batches use
`kafka-batch-apicurio-registry-source`. This Kamelet i [...]
"group" : "Kafka",
"namespace" : "Kafka",
"provider" : "Apache Software Foundation"
diff --git
a/library/camel-kamelets/src/main/resources/kamelets/kafka-apicurio-registry-not-secured-sink.kamelet.yaml
b/library/camel-kamelets/src/main/resources/kamelets/kafka-apicurio-registry-not-secured-sink.kamelet.yaml
index f89050f78..ef6642bf7 100644
---
a/library/camel-kamelets/src/main/resources/kamelets/kafka-apicurio-registry-not-secured-sink.kamelet.yaml
+++
b/library/camel-kamelets/src/main/resources/kamelets/kafka-apicurio-registry-not-secured-sink.kamelet.yaml
@@ -19,7 +19,7 @@ kind: Kamelet
metadata:
name: kafka-apicurio-registry-not-secured-sink
annotations:
- camel.apache.org/kamelet.support.level: "Stable"
+ camel.apache.org/kamelet.support.level: "Deprecated"
camel.apache.org/catalog.version: "4.24.0-SNAPSHOT"
camel.apache.org/kamelet.icon:
"data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4NCjwhLS0gR2VuZXJhdG9yOiBBZG9iZSBJbGx1c3RyYXRvciAxOS4wLjAsIFNWRyBFeHBvcnQgUGx1Zy1JbiAuIFNWRyBWZXJzaW9uOiA2LjAwIEJ1aWxkIDApICAtLT4NCjxzdmcgdmVyc2lvbj0iMS4xIiBpZD0iTGF5ZXJfMSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB4bWxuczp4bGluaz0iaHR0cDovL3d3dy53My5vcmcvMTk5OS94bGluayIgeD0iMHB4IiB5PSIwcHgiDQoJIHZpZXdCb3g9IjAgMCA1MDAgNTAwIiBzdHlsZT0iZW5hYmxlLWJhY2tncm91bmQ6bmV3IDAgMCA1MD
[...]
camel.apache.org/provider: "Apache Software Foundation"
@@ -31,9 +31,9 @@ spec:
definition:
title: "Kafka Not Secured with Apicurio Registry Sink"
description: |-
- Sends each message as an Avro record to a topic in Apache Kafka, with
the schema kept in an Apicurio Registry, and no login or TLS to either.
+ Deprecated, to be removed in a later release: sends each message as an
Avro record to a topic in Apache Kafka, with the schema kept in an Apicurio
Registry, and no login or TLS to either.
- Use it to publish records that other applications read with the schema
of the registry, on a Kafka and a registry that need no login, such as in
development. When the registry is secured with Keycloak use
`kafka-not-secured-apicurio-registry-sink`; for records without a schema use
`kafka-sink`.
+ Use it to publish records that other applications read with the schema
of the registry, on a Kafka and a registry that need no login, such as in
development. When the registry is secured with Keycloak use
`kafka-not-secured-apicurio-registry-sink`; for records without a schema use
`kafka-sink`. This Kamelet is deprecated and will be removed in a later
release, as the Kafka Kamelets are reduced to a few.
Input: the body must be an Avro object, such as an Avro `GenericRecord`
or an object of a class generated from the schema; it is written as Avro
binary. A body of text is written as an Avro string, and so fails unless the
schema is a string. The optional `key` header (or `ce-key`) becomes the key of
the record, and the optional `partition-key` header (or `ce-partitionkey`) is
the number of the partition to write to. The other headers of the message,
except the Camel ones, are sent [...]
diff --git
a/library/camel-kamelets/src/main/resources/kamelets/kafka-apicurio-registry-not-secured-source.kamelet.yaml
b/library/camel-kamelets/src/main/resources/kamelets/kafka-apicurio-registry-not-secured-source.kamelet.yaml
index c6bc40a65..cd1c7c48d 100644
---
a/library/camel-kamelets/src/main/resources/kamelets/kafka-apicurio-registry-not-secured-source.kamelet.yaml
+++
b/library/camel-kamelets/src/main/resources/kamelets/kafka-apicurio-registry-not-secured-source.kamelet.yaml
@@ -19,7 +19,7 @@ kind: Kamelet
metadata:
name: kafka-apicurio-registry-not-secured-source
annotations:
- camel.apache.org/kamelet.support.level: "Preview"
+ camel.apache.org/kamelet.support.level: "Deprecated"
camel.apache.org/catalog.version: "4.24.0-SNAPSHOT"
camel.apache.org/kamelet.icon:
"data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4NCjwhLS0gR2VuZXJhdG9yOiBBZG9iZSBJbGx1c3RyYXRvciAxOS4wLjAsIFNWRyBFeHBvcnQgUGx1Zy1JbiAuIFNWRyBWZXJzaW9uOiA2LjAwIEJ1aWxkIDApICAtLT4NCjxzdmcgdmVyc2lvbj0iMS4xIiBpZD0iTGF5ZXJfMSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB4bWxuczp4bGluaz0iaHR0cDovL3d3dy53My5vcmcvMTk5OS94bGluayIgeD0iMHB4IiB5PSIwcHgiDQoJIHZpZXdCb3g9IjAgMCA1MDAgNTAwIiBzdHlsZT0iZW5hYmxlLWJhY2tncm91bmQ6bmV3IDAgMCA1MD
[...]
camel.apache.org/provider: "Apache Software Foundation"
@@ -31,9 +31,9 @@ spec:
definition:
title: "Kafka Not Secured with Apicurio Registry Source"
description: |-
- Receives each record written with a JSON Schema from topics in Apache
Kafka, with the schema kept in an Apicurio Registry, and no login or TLS to
either.
+ Deprecated, to be removed in a later release: receives each record
written with a JSON Schema from topics in Apache Kafka, with the schema kept in
an Apicurio Registry, and no login or TLS to either.
- Use it to read JSON records that other applications write with a JSON
Schema of the registry, on a Kafka and a registry that need no login, such as
in development. For Avro records use
`kafka-batch-apicurio-registry-not-secured-source`; when the registry is
secured with Keycloak use `kafka-not-secured-apicurio-registry-json-source`;
for records without a schema use `kafka-source`.
+ Use it to read JSON records that other applications write with a JSON
Schema of the registry, on a Kafka and a registry that need no login, such as
in development. For Avro records use
`kafka-batch-apicurio-registry-not-secured-source`; when the registry is
secured with Keycloak use `kafka-not-secured-apicurio-registry-json-source`;
for records without a schema use `kafka-source`. This Kamelet is deprecated and
will be removed in a later release, as the Kafka Kamelets are reduced t [...]
Output: the body is the value of the record as parsed JSON. The
`kafka-topic`, `kafka-key`, `kafka-partition`, `kafka-offset` and
`kafka-timestamp` (in milliseconds since 1970) headers say where the record
came from. They are also set as `ce-kafkatopic`, `ce-kafkakey` and so on, and
as the `CamelKafka*` headers that the Kafka actions read. The record headers
become message headers, as text unless `deserializeHeaders` is false.
diff --git
a/library/camel-kamelets/src/main/resources/kamelets/kafka-batch-apicurio-registry-not-secured-source.kamelet.yaml
b/library/camel-kamelets/src/main/resources/kamelets/kafka-batch-apicurio-registry-not-secured-source.kamelet.yaml
index 29e175114..9d3bb0a5a 100644
---
a/library/camel-kamelets/src/main/resources/kamelets/kafka-batch-apicurio-registry-not-secured-source.kamelet.yaml
+++
b/library/camel-kamelets/src/main/resources/kamelets/kafka-batch-apicurio-registry-not-secured-source.kamelet.yaml
@@ -19,7 +19,7 @@ kind: Kamelet
metadata:
name: kafka-batch-apicurio-registry-not-secured-source
annotations:
- camel.apache.org/kamelet.support.level: "Preview"
+ camel.apache.org/kamelet.support.level: "Deprecated"
camel.apache.org/catalog.version: "4.24.0-SNAPSHOT"
camel.apache.org/kamelet.icon:
"data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4NCjwhLS0gR2VuZXJhdG9yOiBBZG9iZSBJbGx1c3RyYXRvciAxOS4wLjAsIFNWRyBFeHBvcnQgUGx1Zy1JbiAuIFNWRyBWZXJzaW9uOiA2LjAwIEJ1aWxkIDApICAtLT4NCjxzdmcgdmVyc2lvbj0iMS4xIiBpZD0iTGF5ZXJfMSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB4bWxuczp4bGluaz0iaHR0cDovL3d3dy53My5vcmcvMTk5OS94bGluayIgeD0iMHB4IiB5PSIwcHgiDQoJIHZpZXdCb3g9IjAgMCA1MDAgNTAwIiBzdHlsZT0iZW5hYmxlLWJhY2tncm91bmQ6bmV3IDAgMCA1MD
[...]
camel.apache.org/provider: "Apache Software Foundation"
@@ -31,9 +31,9 @@ spec:
definition:
title: "Kafka Batch Not Secured with Apicurio Registry Source"
description: |-
- Receives Avro records from topics in Apache Kafka in batches, with the
schema kept in an Apicurio Registry, and no login or TLS to either.
+ Deprecated, to be removed in a later release: receives Avro records from
topics in Apache Kafka in batches, with the schema kept in an Apicurio
Registry, and no login or TLS to either.
- Use it to read many Avro records at once, as written by
`kafka-apicurio-registry-not-secured-sink`, on a Kafka and a registry that need
no login, such as in development. When the registry is secured with Keycloak
use `kafka-batch-apicurio-registry-source`.
+ Use it to read many Avro records at once, as written by
`kafka-apicurio-registry-not-secured-sink`, on a Kafka and a registry that need
no login, such as in development. When the registry is secured with Keycloak
use `kafka-batch-apicurio-registry-source`. This Kamelet is deprecated and will
be removed in a later release, as the Kafka Kamelets are reduced to a few.
Output: the body is a List with one entry per record, up to `batchSize`.
Each entry is a message of its own, with the value of the record as its body
(an Avro `GenericRecord`, whose text form is JSON), and the key, offset and
timestamp of the record in its `CamelKafkaKey`, `CamelKafkaOffset` and
`CamelKafkaTimestamp` headers. The record headers are in the entries too, as
bytes. The message itself has the `CamelKafkaTopic` and `CamelKafkaPartition`
headers. The `kafka-topic`, `kafka [...]
diff --git
a/library/camel-kamelets/src/main/resources/kamelets/kafka-batch-apicurio-registry-source.kamelet.yaml
b/library/camel-kamelets/src/main/resources/kamelets/kafka-batch-apicurio-registry-source.kamelet.yaml
index f6578e55a..b96815125 100644
---
a/library/camel-kamelets/src/main/resources/kamelets/kafka-batch-apicurio-registry-source.kamelet.yaml
+++
b/library/camel-kamelets/src/main/resources/kamelets/kafka-batch-apicurio-registry-source.kamelet.yaml
@@ -19,7 +19,7 @@ kind: Kamelet
metadata:
name: kafka-batch-apicurio-registry-source
annotations:
- camel.apache.org/kamelet.support.level: "Preview"
+ camel.apache.org/kamelet.support.level: "Deprecated"
camel.apache.org/catalog.version: "4.24.0-SNAPSHOT"
camel.apache.org/kamelet.icon:
"data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4NCjwhLS0gR2VuZXJhdG9yOiBBZG9iZSBJbGx1c3RyYXRvciAxOS4wLjAsIFNWRyBFeHBvcnQgUGx1Zy1JbiAuIFNWRyBWZXJzaW9uOiA2LjAwIEJ1aWxkIDApICAtLT4NCjxzdmcgdmVyc2lvbj0iMS4xIiBpZD0iTGF5ZXJfMSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB4bWxuczp4bGluaz0iaHR0cDovL3d3dy53My5vcmcvMTk5OS94bGluayIgeD0iMHB4IiB5PSIwcHgiDQoJIHZpZXdCb3g9IjAgMCA1MDAgNTAwIiBzdHlsZT0iZW5hYmxlLWJhY2tncm91bmQ6bmV3IDAgMCA1MD
[...]
camel.apache.org/provider: "Apache Software Foundation"
@@ -31,9 +31,9 @@ spec:
definition:
title: "Kafka Batch with Apicurio Registry secured with Keycloak Source"
description: |-
- Receives Avro records from topics in Apache Kafka in batches, with the
schema kept in an Apicurio Registry secured with Keycloak.
+ Deprecated, to be removed in a later release: receives Avro records from
topics in Apache Kafka in batches, with the schema kept in an Apicurio Registry
secured with Keycloak.
- Use it to read many Avro records at once, when the registry needs a
Keycloak login and Kafka needs none. For one record at a time use
`kafka-not-secured-apicurio-registry-source`; when the registry needs no login
use `kafka-batch-apicurio-registry-not-secured-source`.
+ Use it to read many Avro records at once, when the registry needs a
Keycloak login and Kafka needs none. For one record at a time use
`kafka-not-secured-apicurio-registry-source`; when the registry needs no login
use `kafka-batch-apicurio-registry-not-secured-source`. This Kamelet is
deprecated and will be removed in a later release, as the Kafka Kamelets are
reduced to a few.
Output: the body is a List with one entry per record, up to `batchSize`.
Each entry is a message of its own, with the value of the record as its body
(an Avro `GenericRecord`, whose text form is JSON), and the key, offset and
timestamp of the record in its `CamelKafkaKey`, `CamelKafkaOffset` and
`CamelKafkaTimestamp` headers. The record headers are in the entries too, as
bytes. The message itself has the `CamelKafkaTopic` and `CamelKafkaPartition`
headers. The `kafka-topic`, `kafka [...]
diff --git
a/library/camel-kamelets/src/main/resources/kamelets/kafka-not-secured-apicurio-registry-json-source.kamelet.yaml
b/library/camel-kamelets/src/main/resources/kamelets/kafka-not-secured-apicurio-registry-json-source.kamelet.yaml
index 5ee2f1da6..ef5426e4e 100644
---
a/library/camel-kamelets/src/main/resources/kamelets/kafka-not-secured-apicurio-registry-json-source.kamelet.yaml
+++
b/library/camel-kamelets/src/main/resources/kamelets/kafka-not-secured-apicurio-registry-json-source.kamelet.yaml
@@ -19,7 +19,7 @@ kind: Kamelet
metadata:
name: kafka-not-secured-apicurio-registry-json-source
annotations:
- camel.apache.org/kamelet.support.level: "Preview"
+ camel.apache.org/kamelet.support.level: "Deprecated"
camel.apache.org/catalog.version: "4.24.0-SNAPSHOT"
camel.apache.org/kamelet.icon:
"data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4NCjwhLS0gR2VuZXJhdG9yOiBBZG9iZSBJbGx1c3RyYXRvciAxOS4wLjAsIFNWRyBFeHBvcnQgUGx1Zy1JbiAuIFNWRyBWZXJzaW9uOiA2LjAwIEJ1aWxkIDApICAtLT4NCjxzdmcgdmVyc2lvbj0iMS4xIiBpZD0iTGF5ZXJfMSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB4bWxuczp4bGluaz0iaHR0cDovL3d3dy53My5vcmcvMTk5OS94bGluayIgeD0iMHB4IiB5PSIwcHgiDQoJIHZpZXdCb3g9IjAgMCA1MDAgNTAwIiBzdHlsZT0iZW5hYmxlLWJhY2tncm91bmQ6bmV3IDAgMCA1MD
[...]
camel.apache.org/provider: "Apache Software Foundation"
@@ -31,9 +31,9 @@ spec:
definition:
title: "Kafka not secured with Apicurio Registry secured with Keycloak for
JSON schema support Source"
description: |-
- Receives each record written with a JSON Schema from topics in Apache
Kafka, with the schema kept in an Apicurio Registry secured with Keycloak.
+ Deprecated, to be removed in a later release: receives each record
written with a JSON Schema from topics in Apache Kafka, with the schema kept in
an Apicurio Registry secured with Keycloak.
- Use it to read JSON records that other applications write with a JSON
Schema of the registry, when the registry needs a Keycloak login and Kafka
needs none. For Avro records use `kafka-not-secured-apicurio-registry-source`;
when the registry needs no login use
`kafka-apicurio-registry-not-secured-source`.
+ Use it to read JSON records that other applications write with a JSON
Schema of the registry, when the registry needs a Keycloak login and Kafka
needs none. For Avro records use `kafka-not-secured-apicurio-registry-source`;
when the registry needs no login use
`kafka-apicurio-registry-not-secured-source`. This Kamelet is deprecated and
will be removed in a later release, as the Kafka Kamelets are reduced to a few.
Output: the body is the value of the record as parsed JSON. The
`kafka-topic`, `kafka-key`, `kafka-partition`, `kafka-offset` and
`kafka-timestamp` (in milliseconds since 1970) headers say where the record
came from. They are also set as `ce-kafkatopic`, `ce-kafkakey` and so on, and
as the `CamelKafka*` headers that the Kafka actions read. The record headers
become message headers, as text unless `deserializeHeaders` is false.
diff --git
a/library/camel-kamelets/src/main/resources/kamelets/kafka-not-secured-apicurio-registry-sink.kamelet.yaml
b/library/camel-kamelets/src/main/resources/kamelets/kafka-not-secured-apicurio-registry-sink.kamelet.yaml
index c9b922b6a..a3cc8ef1c 100644
---
a/library/camel-kamelets/src/main/resources/kamelets/kafka-not-secured-apicurio-registry-sink.kamelet.yaml
+++
b/library/camel-kamelets/src/main/resources/kamelets/kafka-not-secured-apicurio-registry-sink.kamelet.yaml
@@ -19,7 +19,7 @@ kind: Kamelet
metadata:
name: kafka-not-secured-apicurio-registry-sink
annotations:
- camel.apache.org/kamelet.support.level: "Stable"
+ camel.apache.org/kamelet.support.level: "Deprecated"
camel.apache.org/catalog.version: "4.24.0-SNAPSHOT"
camel.apache.org/kamelet.icon:
"data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4NCjwhLS0gR2VuZXJhdG9yOiBBZG9iZSBJbGx1c3RyYXRvciAxOS4wLjAsIFNWRyBFeHBvcnQgUGx1Zy1JbiAuIFNWRyBWZXJzaW9uOiA2LjAwIEJ1aWxkIDApICAtLT4NCjxzdmcgdmVyc2lvbj0iMS4xIiBpZD0iTGF5ZXJfMSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB4bWxuczp4bGluaz0iaHR0cDovL3d3dy53My5vcmcvMTk5OS94bGluayIgeD0iMHB4IiB5PSIwcHgiDQoJIHZpZXdCb3g9IjAgMCA1MDAgNTAwIiBzdHlsZT0iZW5hYmxlLWJhY2tncm91bmQ6bmV3IDAgMCA1MD
[...]
camel.apache.org/provider: "Apache Software Foundation"
@@ -31,9 +31,9 @@ spec:
definition:
title: "Kafka Not Secured with Apicurio Registry secured with Keycloak
Sink"
description: |-
- Sends each message as an Avro record to a topic in Apache Kafka, with
the schema kept in an Apicurio Registry secured with Keycloak.
+ Deprecated, to be removed in a later release: sends each message as an
Avro record to a topic in Apache Kafka, with the schema kept in an Apicurio
Registry secured with Keycloak.
- Use it to publish records that other applications read with the schema
of the registry, when the registry needs a Keycloak login and Kafka needs none.
When the registry needs no login use
`kafka-apicurio-registry-not-secured-sink`; for records without a schema use
`kafka-sink`.
+ Use it to publish records that other applications read with the schema
of the registry, when the registry needs a Keycloak login and Kafka needs none.
When the registry needs no login use
`kafka-apicurio-registry-not-secured-sink`; for records without a schema use
`kafka-sink`. This Kamelet is deprecated and will be removed in a later
release, as the Kafka Kamelets are reduced to a few.
Input: the body must be an Avro object, such as an Avro `GenericRecord`
or an object of a class generated from the schema; it is written as Avro
binary. A body of text is written as an Avro string, and so fails unless the
schema is a string. The optional `key` header (or `ce-key`) becomes the key of
the record, and the optional `partition-key` header (or `ce-partitionkey`) is
the number of the partition to write to. The other headers of the message,
except the Camel ones, are sent [...]
diff --git
a/library/camel-kamelets/src/main/resources/kamelets/kafka-not-secured-apicurio-registry-source.kamelet.yaml
b/library/camel-kamelets/src/main/resources/kamelets/kafka-not-secured-apicurio-registry-source.kamelet.yaml
index 1c24d1d0e..6be88a031 100644
---
a/library/camel-kamelets/src/main/resources/kamelets/kafka-not-secured-apicurio-registry-source.kamelet.yaml
+++
b/library/camel-kamelets/src/main/resources/kamelets/kafka-not-secured-apicurio-registry-source.kamelet.yaml
@@ -19,7 +19,7 @@ kind: Kamelet
metadata:
name: kafka-not-secured-apicurio-registry-source
annotations:
- camel.apache.org/kamelet.support.level: "Preview"
+ camel.apache.org/kamelet.support.level: "Deprecated"
camel.apache.org/catalog.version: "4.24.0-SNAPSHOT"
camel.apache.org/kamelet.icon:
"data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4NCjwhLS0gR2VuZXJhdG9yOiBBZG9iZSBJbGx1c3RyYXRvciAxOS4wLjAsIFNWRyBFeHBvcnQgUGx1Zy1JbiAuIFNWRyBWZXJzaW9uOiA2LjAwIEJ1aWxkIDApICAtLT4NCjxzdmcgdmVyc2lvbj0iMS4xIiBpZD0iTGF5ZXJfMSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB4bWxuczp4bGluaz0iaHR0cDovL3d3dy53My5vcmcvMTk5OS94bGluayIgeD0iMHB4IiB5PSIwcHgiDQoJIHZpZXdCb3g9IjAgMCA1MDAgNTAwIiBzdHlsZT0iZW5hYmxlLWJhY2tncm91bmQ6bmV3IDAgMCA1MD
[...]
camel.apache.org/provider: "Apache Software Foundation"
@@ -31,9 +31,9 @@ spec:
definition:
title: "Kafka not secured with Apicurio Registry secured with Keycloak
Source"
description: |-
- Receives each Avro record from topics in Apache Kafka, with the schema
kept in an Apicurio Registry secured with Keycloak.
+ Deprecated, to be removed in a later release: receives each Avro record
from topics in Apache Kafka, with the schema kept in an Apicurio Registry
secured with Keycloak.
- Use it to read Avro records, as written by
`kafka-not-secured-apicurio-registry-sink`, when the registry needs a Keycloak
login and Kafka needs none. For JSON Schema records use
`kafka-not-secured-apicurio-registry-json-source`; for batches use
`kafka-batch-apicurio-registry-source`.
+ Use it to read Avro records, as written by
`kafka-not-secured-apicurio-registry-sink`, when the registry needs a Keycloak
login and Kafka needs none. For JSON Schema records use
`kafka-not-secured-apicurio-registry-json-source`; for batches use
`kafka-batch-apicurio-registry-source`. This Kamelet is deprecated and will be
removed in a later release, as the Kafka Kamelets are reduced to a few.
Output: the body is the value of the record as an Avro `GenericRecord`,
whose text form is JSON. The `kafka-topic`, `kafka-key`, `kafka-partition`,
`kafka-offset` and `kafka-timestamp` (in milliseconds since 1970) headers say
where the record came from. They are also set as `ce-kafkatopic`, `ce-kafkakey`
and so on, and as the `CamelKafka*` headers that the Kafka actions read. The
record headers become message headers, as text unless `deserializeHeaders` is
false.