[camel] branch main updated: CAMEL-18366: camel-yaml-dsl - Allow to configure route options in route-templates/kamelets.

[da...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/main by this push:
     new a080904e750 CAMEL-18366: camel-yaml-dsl - Allow to configure route options in route-templates/kamelets.
a080904e750 is described below

commit a080904e750d8e1c656dada4681e142618be0d1b
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Wed Aug 10 14:02:38 2022 +0200

    CAMEL-18366: camel-yaml-dsl - Allow to configure route options in route-templates/kamelets.
---
 .../ROOT/pages/camel-3x-upgrade-guide-3_19.adoc    | 25 ++++++++++++++++++++++
 1 file changed, 25 insertions(+)

diff --git a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_19.adoc b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_19.adoc
index 483ba331c62..b9440888adf 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_19.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_19.adoc
@@ -16,6 +16,31 @@ Removed using `template` as a custom alias for `routeTemplate` or `route-templat
 
 Removed the `tod` custom alias for `toD` or `to-d`.
 
+A route template can now also define a `route` which allows specifying route
+options that otherwise is not possible when using `from`.
+
+For example, you can now disable stream-caching, as shown in the snippet below that are from a Kamelet:
+
+[source,yaml]
+----
+spec:
+  template:
+    route:
+      stream-caching: false
+      message-history: true
+      from:
+        uri: timer:tick
+        parameters:
+          period: "{{period}}"
+        steps:
+          - set-body:
+              constant: "{{message}}"
+          - set-header:
+              name: "Content-Type"
+              constant: "{{contentType}}"
+          - to: kamelet:sink
+----
+
 === camel-salesforce
 
 The URI format for consumer operations has changed. All consumer URIs now use the `subscribe` operation. E.g., `salesforce:subscribe:<topic_name>`, `salesforce:subscribe:event/<event_name>`, `salesforce:subscribe:data/ChangeEvents`.