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 1c3a19c37 chore: pulsar-source and pulsar-sink can trust a private CA 
with tlsTrustCertsFilePath (#3170) (#3256)
1c3a19c37 is described below

commit 1c3a19c37e37008a14ef38096ead4bd73be93152
Author: Claus Ibsen <[email protected]>
AuthorDate: Thu Nov 19 13:27:34 2026 +0100

    chore: pulsar-source and pulsar-sink can trust a private CA with 
tlsTrustCertsFilePath (#3170) (#3256)
    
    CAMEL-27196 gives camel-pulsar the tlsTrustCertsFilePath option, a PEM
    file with the certificate authorities to trust for pulsar+ssl://. The
    descriptions no longer send users to the JVM trust store, and say that
    the certificate must be issued for the host name (CAMEL-27207).
    
    Co-authored-by: Claude Opus 5.5 <[email protected]>
---
 kamelets/pulsar-sink.kamelet.yaml                                | 9 +++++++--
 kamelets/pulsar-source.kamelet.yaml                              | 9 +++++++--
 .../src/main/resources/META-INF/kamelets-index.json              | 4 ++--
 .../src/main/resources/kamelets/pulsar-sink.kamelet.yaml         | 9 +++++++--
 .../src/main/resources/kamelets/pulsar-source.kamelet.yaml       | 9 +++++++--
 5 files changed, 30 insertions(+), 10 deletions(-)

diff --git a/kamelets/pulsar-sink.kamelet.yaml 
b/kamelets/pulsar-sink.kamelet.yaml
index f75984838..a89fb7fb4 100644
--- a/kamelets/pulsar-sink.kamelet.yaml
+++ b/kamelets/pulsar-sink.kamelet.yaml
@@ -57,7 +57,7 @@ spec:
 
       Output: the message is unchanged.
 
-      Good to know: it connects with no TLS and no login, unless `serviceUrl` 
starts with `pulsar+ssl://` and `authenticationClass` is set. Over TLS, the 
certificate of Pulsar must be signed by an authority that the Java trust store 
of the integration trusts; for a private one, point `javax.net.ssl.trustStore` 
at a trust store with it, as the Kamelet has no trust store option. It connects 
when the integration starts, and the integration fails to start when Pulsar 
cannot be reached, unles [...]
+      Good to know: it connects with no TLS and no login, unless `serviceUrl` 
starts with `pulsar+ssl://` and `authenticationClass` is set. Over TLS, the 
certificate of Pulsar must be signed by an authority that the Java trust store 
of the integration trusts, or by one in the PEM file of 
`tlsTrustCertsFilePath`, such as a private one, and it must be issued for the 
host name in `serviceUrl`. It connects when the integration starts, and the 
integration fails to start when Pulsar cannot be  [...]
     required:
       - topicType
       - topic
@@ -90,6 +90,11 @@ spec:
         description: "The address of the Pulsar broker, as 
`pulsar://host:port` (the usual port is 6650), or `pulsar+ssl://host:port` for 
TLS (usually 6651)."
         example: "pulsar://localhost:6650"
         type: string        
+      tlsTrustCertsFilePath:
+        title: "TLS Trust Certificates File"
+        description: "The path of a PEM file with the certificates of the 
authorities to trust for a `pulsar+ssl://` broker, such as a private one, 
instead of the Java trust store. Only used with `pulsar+ssl://`."
+        type: string
+        example: "/etc/pulsar/ca.pem"
       authenticationClass:
         title: "Authentication Class"
         description: "The Java class of the Pulsar authentication plugin to 
log in with, such as `org.apache.pulsar.client.impl.auth.AuthenticationToken` 
for a token. Leave it empty for a Pulsar without login."
@@ -175,4 +180,4 @@ spec:
                         simple:
                           expression: "${header[key]}"
         - to:
-            uri: 
"pulsar:{{topicType}}/{{tenant}}/{{namespaceName}}/{{topic}}?authenticationClass={{?authenticationClass}}&authenticationParams={{?authenticationParams}}&batchingEnabled={{?batchingEnabled}}&batchingMaxMessages={{?batchingMaxMessages}}&batchingMaxPublishDelayMicros={{?batchingMaxPublishDelayMicros}}&blockIfQueueFull={{?blockIfQueueFull}}&compressionType={{?compressionType}}&initialSequenceId={{?initialSequenceId}}&lazyStartProducer={{?lazyStart}}&maxPendingMessages={{?max
 [...]
+            uri: 
"pulsar:{{topicType}}/{{tenant}}/{{namespaceName}}/{{topic}}?authenticationClass={{?authenticationClass}}&authenticationParams={{?authenticationParams}}&batchingEnabled={{?batchingEnabled}}&batchingMaxMessages={{?batchingMaxMessages}}&batchingMaxPublishDelayMicros={{?batchingMaxPublishDelayMicros}}&blockIfQueueFull={{?blockIfQueueFull}}&compressionType={{?compressionType}}&initialSequenceId={{?initialSequenceId}}&lazyStartProducer={{?lazyStart}}&maxPendingMessages={{?max
 [...]
diff --git a/kamelets/pulsar-source.kamelet.yaml 
b/kamelets/pulsar-source.kamelet.yaml
index 97ab41d26..fe2db6fb7 100644
--- a/kamelets/pulsar-source.kamelet.yaml
+++ b/kamelets/pulsar-source.kamelet.yaml
@@ -63,7 +63,7 @@ spec:
 
       Output: the body is the payload, as bytes. The headers give the topic 
(`topic_name`), the key (`key`), the Pulsar properties as a Map (`properties`), 
the `message_id`, the `publish_time` and the `producer_name`.
 
-      Good to know: the subscription (`subscriptionName`, `subs` by default) 
remembers what was read, so messages sent while the source is stopped are read 
when it starts again. A new subscription starts at the newest message, unless 
`subscriptionInitialPosition` is `EARLIEST`. A message whose processing fails 
is delivered again after one minute, again and again, unless 
`maxRedeliverCount` is set with a `SHARED` or `KEY_SHARED` subscription. A 
message whose processing takes longer than ` [...]
+      Good to know: the subscription (`subscriptionName`, `subs` by default) 
remembers what was read, so messages sent while the source is stopped are read 
when it starts again. A new subscription starts at the newest message, unless 
`subscriptionInitialPosition` is `EARLIEST`. A message whose processing fails 
is delivered again after one minute, again and again, unless 
`maxRedeliverCount` is set with a `SHARED` or `KEY_SHARED` subscription. A 
message whose processing takes longer than ` [...]
     required:
       - topicType
       - topic
@@ -96,6 +96,11 @@ spec:
         description: "The address of the Pulsar broker, as 
`pulsar://host:port` (the usual port is 6650), or `pulsar+ssl://host:port` for 
TLS (usually 6651)."
         example: "pulsar://localhost:6650"
         type: string        
+      tlsTrustCertsFilePath:
+        title: "TLS Trust Certificates File"
+        description: "The path of a PEM file with the certificates of the 
authorities to trust for a `pulsar+ssl://` broker, such as a private one, 
instead of the Java trust store. Only used with `pulsar+ssl://`."
+        type: string
+        example: "/etc/pulsar/ca.pem"
       ackTimeoutMillis:
         title: "Acknowledgement Timeout"
         description: "How long the processing of a message may take, in 
milliseconds. A message that is not done by then is delivered again, and so 
processed twice. When it is not set, 10000 (10 seconds). 0 turns this off; a 
value from 1 to 999 makes the integration fail to start."
@@ -183,7 +188,7 @@ spec:
     type: object
   template:
     from:
-      uri: 
"pulsar:{{topicType}}/{{tenant}}/{{namespaceName}}/{{topic}}?ackTimeoutMillis={{?ackTimeoutMillis}}&authenticationClass={{?authenticationClass}}&authenticationParams={{?authenticationParams}}&consumerNamePrefix={{?consumerNamePrefix}}&consumerQueueSize={{?consumerQueueSize}}&deadLetterTopic={{?deadLetterTopic}}&maxRedeliverCount={{?maxRedeliverCount}}&messageListener={{?messageListener}}&negativeAckRedeliveryDelayMicros={{?negativeAckRedeliveryDelayMicros}}&numberOfConsumerThr
 [...]
+      uri: 
"pulsar:{{topicType}}/{{tenant}}/{{namespaceName}}/{{topic}}?ackTimeoutMillis={{?ackTimeoutMillis}}&authenticationClass={{?authenticationClass}}&authenticationParams={{?authenticationParams}}&consumerNamePrefix={{?consumerNamePrefix}}&consumerQueueSize={{?consumerQueueSize}}&deadLetterTopic={{?deadLetterTopic}}&maxRedeliverCount={{?maxRedeliverCount}}&messageListener={{?messageListener}}&negativeAckRedeliveryDelayMicros={{?negativeAckRedeliveryDelayMicros}}&numberOfConsumerThr
 [...]
       steps:
         - to:
             uri: kamelet:sink
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 b839cbf91..36a54fb20 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
@@ -1745,7 +1745,7 @@
     "supportLevel" : "Stable",
     "title" : "Pulsar Sink",
     "summary" : "Sends each message to a topic in Apache Pulsar, named by its 
tenant, namespace and topic name.",
-    "description" : "Sends each message to a topic in Apache Pulsar, named by 
its tenant, namespace and topic name.\n\nUse it to publish events or data for 
other applications to read from Pulsar, such as orders or sensor readings. Use 
`pulsar-source` to read them.\n\nInput: the body is the payload, as text or 
bytes. A Map fails: turn it into JSON text first, for example with 
`json-serialize-action`. The headers of the message are not sent as Pulsar 
properties; to set properties, put a Ma [...]
+    "description" : "Sends each message to a topic in Apache Pulsar, named by 
its tenant, namespace and topic name.\n\nUse it to publish events or data for 
other applications to read from Pulsar, such as orders or sensor readings. Use 
`pulsar-source` to read them.\n\nInput: the body is the payload, as text or 
bytes. A Map fails: turn it into JSON text first, for example with 
`json-serialize-action`. The headers of the message are not sent as Pulsar 
properties; to set properties, put a Ma [...]
     "group" : "Pulsar",
     "namespace" : "Messaging",
     "provider" : "Apache Software Foundation"
@@ -1755,7 +1755,7 @@
     "supportLevel" : "Stable",
     "title" : "Pulsar Source",
     "summary" : "Receives each message from a topic in Apache Pulsar, or from 
every topic whose name matches a pattern, through a named subscription.",
-    "description" : "Receives each message from a topic in Apache Pulsar, or 
from every topic whose name matches a pattern, through a named 
subscription.\n\nUse it to process events or data that other applications 
publish to Pulsar. Several copies can share the work with a `SHARED` or 
`KEY_SHARED` subscription.\n\nOutput: the body is the payload, as bytes. The 
headers give the topic (`topic_name`), the key (`key`), the Pulsar properties 
as a Map (`properties`), the `message_id`, the `pub [...]
+    "description" : "Receives each message from a topic in Apache Pulsar, or 
from every topic whose name matches a pattern, through a named 
subscription.\n\nUse it to process events or data that other applications 
publish to Pulsar. Several copies can share the work with a `SHARED` or 
`KEY_SHARED` subscription.\n\nOutput: the body is the payload, as bytes. The 
headers give the topic (`topic_name`), the key (`key`), the Pulsar properties 
as a Map (`properties`), the `message_id`, the `pub [...]
     "group" : "Pulsar",
     "namespace" : "Messaging",
     "provider" : "Apache Software Foundation"
diff --git 
a/library/camel-kamelets/src/main/resources/kamelets/pulsar-sink.kamelet.yaml 
b/library/camel-kamelets/src/main/resources/kamelets/pulsar-sink.kamelet.yaml
index f75984838..a89fb7fb4 100644
--- 
a/library/camel-kamelets/src/main/resources/kamelets/pulsar-sink.kamelet.yaml
+++ 
b/library/camel-kamelets/src/main/resources/kamelets/pulsar-sink.kamelet.yaml
@@ -57,7 +57,7 @@ spec:
 
       Output: the message is unchanged.
 
-      Good to know: it connects with no TLS and no login, unless `serviceUrl` 
starts with `pulsar+ssl://` and `authenticationClass` is set. Over TLS, the 
certificate of Pulsar must be signed by an authority that the Java trust store 
of the integration trusts; for a private one, point `javax.net.ssl.trustStore` 
at a trust store with it, as the Kamelet has no trust store option. It connects 
when the integration starts, and the integration fails to start when Pulsar 
cannot be reached, unles [...]
+      Good to know: it connects with no TLS and no login, unless `serviceUrl` 
starts with `pulsar+ssl://` and `authenticationClass` is set. Over TLS, the 
certificate of Pulsar must be signed by an authority that the Java trust store 
of the integration trusts, or by one in the PEM file of 
`tlsTrustCertsFilePath`, such as a private one, and it must be issued for the 
host name in `serviceUrl`. It connects when the integration starts, and the 
integration fails to start when Pulsar cannot be  [...]
     required:
       - topicType
       - topic
@@ -90,6 +90,11 @@ spec:
         description: "The address of the Pulsar broker, as 
`pulsar://host:port` (the usual port is 6650), or `pulsar+ssl://host:port` for 
TLS (usually 6651)."
         example: "pulsar://localhost:6650"
         type: string        
+      tlsTrustCertsFilePath:
+        title: "TLS Trust Certificates File"
+        description: "The path of a PEM file with the certificates of the 
authorities to trust for a `pulsar+ssl://` broker, such as a private one, 
instead of the Java trust store. Only used with `pulsar+ssl://`."
+        type: string
+        example: "/etc/pulsar/ca.pem"
       authenticationClass:
         title: "Authentication Class"
         description: "The Java class of the Pulsar authentication plugin to 
log in with, such as `org.apache.pulsar.client.impl.auth.AuthenticationToken` 
for a token. Leave it empty for a Pulsar without login."
@@ -175,4 +180,4 @@ spec:
                         simple:
                           expression: "${header[key]}"
         - to:
-            uri: 
"pulsar:{{topicType}}/{{tenant}}/{{namespaceName}}/{{topic}}?authenticationClass={{?authenticationClass}}&authenticationParams={{?authenticationParams}}&batchingEnabled={{?batchingEnabled}}&batchingMaxMessages={{?batchingMaxMessages}}&batchingMaxPublishDelayMicros={{?batchingMaxPublishDelayMicros}}&blockIfQueueFull={{?blockIfQueueFull}}&compressionType={{?compressionType}}&initialSequenceId={{?initialSequenceId}}&lazyStartProducer={{?lazyStart}}&maxPendingMessages={{?max
 [...]
+            uri: 
"pulsar:{{topicType}}/{{tenant}}/{{namespaceName}}/{{topic}}?authenticationClass={{?authenticationClass}}&authenticationParams={{?authenticationParams}}&batchingEnabled={{?batchingEnabled}}&batchingMaxMessages={{?batchingMaxMessages}}&batchingMaxPublishDelayMicros={{?batchingMaxPublishDelayMicros}}&blockIfQueueFull={{?blockIfQueueFull}}&compressionType={{?compressionType}}&initialSequenceId={{?initialSequenceId}}&lazyStartProducer={{?lazyStart}}&maxPendingMessages={{?max
 [...]
diff --git 
a/library/camel-kamelets/src/main/resources/kamelets/pulsar-source.kamelet.yaml 
b/library/camel-kamelets/src/main/resources/kamelets/pulsar-source.kamelet.yaml
index 97ab41d26..fe2db6fb7 100644
--- 
a/library/camel-kamelets/src/main/resources/kamelets/pulsar-source.kamelet.yaml
+++ 
b/library/camel-kamelets/src/main/resources/kamelets/pulsar-source.kamelet.yaml
@@ -63,7 +63,7 @@ spec:
 
       Output: the body is the payload, as bytes. The headers give the topic 
(`topic_name`), the key (`key`), the Pulsar properties as a Map (`properties`), 
the `message_id`, the `publish_time` and the `producer_name`.
 
-      Good to know: the subscription (`subscriptionName`, `subs` by default) 
remembers what was read, so messages sent while the source is stopped are read 
when it starts again. A new subscription starts at the newest message, unless 
`subscriptionInitialPosition` is `EARLIEST`. A message whose processing fails 
is delivered again after one minute, again and again, unless 
`maxRedeliverCount` is set with a `SHARED` or `KEY_SHARED` subscription. A 
message whose processing takes longer than ` [...]
+      Good to know: the subscription (`subscriptionName`, `subs` by default) 
remembers what was read, so messages sent while the source is stopped are read 
when it starts again. A new subscription starts at the newest message, unless 
`subscriptionInitialPosition` is `EARLIEST`. A message whose processing fails 
is delivered again after one minute, again and again, unless 
`maxRedeliverCount` is set with a `SHARED` or `KEY_SHARED` subscription. A 
message whose processing takes longer than ` [...]
     required:
       - topicType
       - topic
@@ -96,6 +96,11 @@ spec:
         description: "The address of the Pulsar broker, as 
`pulsar://host:port` (the usual port is 6650), or `pulsar+ssl://host:port` for 
TLS (usually 6651)."
         example: "pulsar://localhost:6650"
         type: string        
+      tlsTrustCertsFilePath:
+        title: "TLS Trust Certificates File"
+        description: "The path of a PEM file with the certificates of the 
authorities to trust for a `pulsar+ssl://` broker, such as a private one, 
instead of the Java trust store. Only used with `pulsar+ssl://`."
+        type: string
+        example: "/etc/pulsar/ca.pem"
       ackTimeoutMillis:
         title: "Acknowledgement Timeout"
         description: "How long the processing of a message may take, in 
milliseconds. A message that is not done by then is delivered again, and so 
processed twice. When it is not set, 10000 (10 seconds). 0 turns this off; a 
value from 1 to 999 makes the integration fail to start."
@@ -183,7 +188,7 @@ spec:
     type: object
   template:
     from:
-      uri: 
"pulsar:{{topicType}}/{{tenant}}/{{namespaceName}}/{{topic}}?ackTimeoutMillis={{?ackTimeoutMillis}}&authenticationClass={{?authenticationClass}}&authenticationParams={{?authenticationParams}}&consumerNamePrefix={{?consumerNamePrefix}}&consumerQueueSize={{?consumerQueueSize}}&deadLetterTopic={{?deadLetterTopic}}&maxRedeliverCount={{?maxRedeliverCount}}&messageListener={{?messageListener}}&negativeAckRedeliveryDelayMicros={{?negativeAckRedeliveryDelayMicros}}&numberOfConsumerThr
 [...]
+      uri: 
"pulsar:{{topicType}}/{{tenant}}/{{namespaceName}}/{{topic}}?ackTimeoutMillis={{?ackTimeoutMillis}}&authenticationClass={{?authenticationClass}}&authenticationParams={{?authenticationParams}}&consumerNamePrefix={{?consumerNamePrefix}}&consumerQueueSize={{?consumerQueueSize}}&deadLetterTopic={{?deadLetterTopic}}&maxRedeliverCount={{?maxRedeliverCount}}&messageListener={{?messageListener}}&negativeAckRedeliveryDelayMicros={{?negativeAckRedeliveryDelayMicros}}&numberOfConsumerThr
 [...]
       steps:
         - to:
             uri: kamelet:sink

Reply via email to