You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by pc...@apache.org on 2024/01/12 14:23:12 UTC
(camel-k) branch main updated (277124770 -> 4ae21a29d)
This is an automated email from the ASF dual-hosted git repository.
pcongiusti pushed a change to branch main
in repository https://gitbox.apache.org/repos/asf/camel-k.git
from 277124770 feat(pipeline): support custom user id execution
new 083a3b6ca doc: add languages section
new 4ae21a29d fix: minor typo
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
cmd/util/doc-gen/main.go | 2 +-
.../bases/camel.apache.org_integrationkits.yaml | 2 +-
.../camel.apache.org_integrationplatforms.yaml | 4 +-
.../crd/bases/camel.apache.org_integrations.yaml | 2 +-
.../bases/camel.apache.org_kameletbindings.yaml | 3 +-
config/crd/bases/camel.apache.org_pipes.yaml | 3 +-
docs/antora.yml | 1 -
docs/modules/ROOT/nav-end.adoc | 97 --------
docs/modules/ROOT/nav.adoc | 105 ++++++++
docs/modules/ROOT/pages/languages/groovy.adoc | 194 +++++++++++++++
docs/modules/ROOT/pages/languages/java.adoc | 25 ++
docs/modules/ROOT/pages/languages/javascript.adoc | 38 +++
docs/modules/ROOT/pages/languages/jsh.adoc | 25 ++
docs/modules/ROOT/pages/languages/kotlin.adoc | 124 ++++++++++
docs/modules/ROOT/pages/languages/languages.adoc | 20 ++
docs/modules/ROOT/pages/languages/xml.adoc | 23 ++
docs/modules/ROOT/pages/languages/yaml.adoc | 263 +++++++++++++++++++++
docs/modules/ROOT/partials/apis/camel-k-crds.adoc | 2 +-
docs/modules/traits/pages/builder.adoc | 2 +-
helm/camel-k/crds/crd-integration-kit.yaml | 2 +-
helm/camel-k/crds/crd-integration-platform.yaml | 4 +-
helm/camel-k/crds/crd-integration.yaml | 2 +-
helm/camel-k/crds/crd-kamelet-binding.yaml | 3 +-
helm/camel-k/crds/crd-pipe.yaml | 3 +-
resources/traits.yaml | 2 +-
25 files changed, 837 insertions(+), 114 deletions(-)
delete mode 100644 docs/modules/ROOT/nav-end.adoc
create mode 100644 docs/modules/ROOT/pages/languages/groovy.adoc
create mode 100644 docs/modules/ROOT/pages/languages/java.adoc
create mode 100644 docs/modules/ROOT/pages/languages/javascript.adoc
create mode 100644 docs/modules/ROOT/pages/languages/jsh.adoc
create mode 100644 docs/modules/ROOT/pages/languages/kotlin.adoc
create mode 100644 docs/modules/ROOT/pages/languages/languages.adoc
create mode 100644 docs/modules/ROOT/pages/languages/xml.adoc
create mode 100644 docs/modules/ROOT/pages/languages/yaml.adoc
(camel-k) 02/02: fix: minor typo
Posted by pc...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
pcongiusti pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-k.git
commit 4ae21a29dfffedbe74b5bdc412ab3b952afe86d3
Author: Pasquale Congiusti <pa...@gmail.com>
AuthorDate: Fri Jan 12 15:15:37 2024 +0100
fix: minor typo
---
config/crd/bases/camel.apache.org_integrationkits.yaml | 2 +-
config/crd/bases/camel.apache.org_integrationplatforms.yaml | 4 ++--
config/crd/bases/camel.apache.org_integrations.yaml | 2 +-
config/crd/bases/camel.apache.org_kameletbindings.yaml | 3 ++-
config/crd/bases/camel.apache.org_pipes.yaml | 3 ++-
docs/modules/ROOT/partials/apis/camel-k-crds.adoc | 2 +-
docs/modules/traits/pages/builder.adoc | 2 +-
helm/camel-k/crds/crd-integration-kit.yaml | 2 +-
helm/camel-k/crds/crd-integration-platform.yaml | 4 ++--
helm/camel-k/crds/crd-integration.yaml | 2 +-
helm/camel-k/crds/crd-kamelet-binding.yaml | 3 ++-
helm/camel-k/crds/crd-pipe.yaml | 3 ++-
resources/traits.yaml | 2 +-
13 files changed, 19 insertions(+), 15 deletions(-)
diff --git a/config/crd/bases/camel.apache.org_integrationkits.yaml b/config/crd/bases/camel.apache.org_integrationkits.yaml
index 6ec3bd07d..72b9037b8 100644
--- a/config/crd/bases/camel.apache.org_integrationkits.yaml
+++ b/config/crd/bases/camel.apache.org_integrationkits.yaml
@@ -289,7 +289,7 @@ spec:
in a csv format, ie, `<taskName1>,<taskName2>,...`. Mind
that you must include also the operator tasks (`builder`,
`quarkus-native`, `package`, `jib`, `spectrum`, `s2i`) if
- you need to execute them. Useful only wih `pod` strategy.
+ you need to execute them. Useful only with `pod` strategy.
type: string
tasksLimitCPU:
description: A list of limit cpu configuration for the specific
diff --git a/config/crd/bases/camel.apache.org_integrationplatforms.yaml b/config/crd/bases/camel.apache.org_integrationplatforms.yaml
index 9a7c238c9..85ae39af3 100644
--- a/config/crd/bases/camel.apache.org_integrationplatforms.yaml
+++ b/config/crd/bases/camel.apache.org_integrationplatforms.yaml
@@ -594,7 +594,7 @@ spec:
in a csv format, ie, `<taskName1>,<taskName2>,...`. Mind
that you must include also the operator tasks (`builder`,
`quarkus-native`, `package`, `jib`, `spectrum`, `s2i`) if
- you need to execute them. Useful only wih `pod` strategy.
+ you need to execute them. Useful only with `pod` strategy.
type: string
tasksLimitCPU:
description: A list of limit cpu configuration for the specific
@@ -2484,7 +2484,7 @@ spec:
in a csv format, ie, `<taskName1>,<taskName2>,...`. Mind
that you must include also the operator tasks (`builder`,
`quarkus-native`, `package`, `jib`, `spectrum`, `s2i`) if
- you need to execute them. Useful only wih `pod` strategy.
+ you need to execute them. Useful only with `pod` strategy.
type: string
tasksLimitCPU:
description: A list of limit cpu configuration for the specific
diff --git a/config/crd/bases/camel.apache.org_integrations.yaml b/config/crd/bases/camel.apache.org_integrations.yaml
index f0018b106..1a25cc2cb 100644
--- a/config/crd/bases/camel.apache.org_integrations.yaml
+++ b/config/crd/bases/camel.apache.org_integrations.yaml
@@ -6507,7 +6507,7 @@ spec:
in a csv format, ie, `<taskName1>,<taskName2>,...`. Mind
that you must include also the operator tasks (`builder`,
`quarkus-native`, `package`, `jib`, `spectrum`, `s2i`) if
- you need to execute them. Useful only wih `pod` strategy.
+ you need to execute them. Useful only with `pod` strategy.
type: string
tasksLimitCPU:
description: A list of limit cpu configuration for the specific
diff --git a/config/crd/bases/camel.apache.org_kameletbindings.yaml b/config/crd/bases/camel.apache.org_kameletbindings.yaml
index cc0b8e10e..6b119dfa4 100644
--- a/config/crd/bases/camel.apache.org_kameletbindings.yaml
+++ b/config/crd/bases/camel.apache.org_kameletbindings.yaml
@@ -6791,7 +6791,8 @@ spec:
in a csv format, ie, `<taskName1>,<taskName2>,...`.
Mind that you must include also the operator tasks (`builder`,
`quarkus-native`, `package`, `jib`, `spectrum`, `s2i`)
- if you need to execute them. Useful only wih `pod` strategy.
+ if you need to execute them. Useful only with `pod`
+ strategy.
type: string
tasksLimitCPU:
description: A list of limit cpu configuration for the
diff --git a/config/crd/bases/camel.apache.org_pipes.yaml b/config/crd/bases/camel.apache.org_pipes.yaml
index 35e8fdc8c..223dbb9fc 100644
--- a/config/crd/bases/camel.apache.org_pipes.yaml
+++ b/config/crd/bases/camel.apache.org_pipes.yaml
@@ -6789,7 +6789,8 @@ spec:
in a csv format, ie, `<taskName1>,<taskName2>,...`.
Mind that you must include also the operator tasks (`builder`,
`quarkus-native`, `package`, `jib`, `spectrum`, `s2i`)
- if you need to execute them. Useful only wih `pod` strategy.
+ if you need to execute them. Useful only with `pod`
+ strategy.
type: string
tasksLimitCPU:
description: A list of limit cpu configuration for the
diff --git a/docs/modules/ROOT/partials/apis/camel-k-crds.adoc b/docs/modules/ROOT/partials/apis/camel-k-crds.adoc
index 16a74cf3a..7cafb6fc3 100644
--- a/docs/modules/ROOT/partials/apis/camel-k-crds.adoc
+++ b/docs/modules/ROOT/partials/apis/camel-k-crds.adoc
@@ -5908,7 +5908,7 @@ string
A list of tasks sorted by the order of execution in a csv format, ie, `<taskName1>,<taskName2>,...`.
Mind that you must include also the operator tasks (`builder`, `quarkus-native`, `package`, `jib`, `spectrum`, `s2i`)
-if you need to execute them. Useful only wih `pod` strategy.
+if you need to execute them. Useful only with `pod` strategy.
|`tasksRequestCPU` +
[]string
diff --git a/docs/modules/traits/pages/builder.adoc b/docs/modules/traits/pages/builder.adoc
index 8560b38f9..4c642821f 100755
--- a/docs/modules/traits/pages/builder.adoc
+++ b/docs/modules/traits/pages/builder.adoc
@@ -86,7 +86,7 @@ Syntax: [configmap\|secret]:name[/key], where name represents the resource name,
| string
| A list of tasks sorted by the order of execution in a csv format, ie, `<taskName1>,<taskName2>,...`.
Mind that you must include also the operator tasks (`builder`, `quarkus-native`, `package`, `jib`, `spectrum`, `s2i`)
-if you need to execute them. Useful only wih `pod` strategy.
+if you need to execute them. Useful only with `pod` strategy.
| builder.tasks-request-cpu
| []string
diff --git a/helm/camel-k/crds/crd-integration-kit.yaml b/helm/camel-k/crds/crd-integration-kit.yaml
index 6ec3bd07d..72b9037b8 100644
--- a/helm/camel-k/crds/crd-integration-kit.yaml
+++ b/helm/camel-k/crds/crd-integration-kit.yaml
@@ -289,7 +289,7 @@ spec:
in a csv format, ie, `<taskName1>,<taskName2>,...`. Mind
that you must include also the operator tasks (`builder`,
`quarkus-native`, `package`, `jib`, `spectrum`, `s2i`) if
- you need to execute them. Useful only wih `pod` strategy.
+ you need to execute them. Useful only with `pod` strategy.
type: string
tasksLimitCPU:
description: A list of limit cpu configuration for the specific
diff --git a/helm/camel-k/crds/crd-integration-platform.yaml b/helm/camel-k/crds/crd-integration-platform.yaml
index 9a7c238c9..85ae39af3 100644
--- a/helm/camel-k/crds/crd-integration-platform.yaml
+++ b/helm/camel-k/crds/crd-integration-platform.yaml
@@ -594,7 +594,7 @@ spec:
in a csv format, ie, `<taskName1>,<taskName2>,...`. Mind
that you must include also the operator tasks (`builder`,
`quarkus-native`, `package`, `jib`, `spectrum`, `s2i`) if
- you need to execute them. Useful only wih `pod` strategy.
+ you need to execute them. Useful only with `pod` strategy.
type: string
tasksLimitCPU:
description: A list of limit cpu configuration for the specific
@@ -2484,7 +2484,7 @@ spec:
in a csv format, ie, `<taskName1>,<taskName2>,...`. Mind
that you must include also the operator tasks (`builder`,
`quarkus-native`, `package`, `jib`, `spectrum`, `s2i`) if
- you need to execute them. Useful only wih `pod` strategy.
+ you need to execute them. Useful only with `pod` strategy.
type: string
tasksLimitCPU:
description: A list of limit cpu configuration for the specific
diff --git a/helm/camel-k/crds/crd-integration.yaml b/helm/camel-k/crds/crd-integration.yaml
index f0018b106..1a25cc2cb 100644
--- a/helm/camel-k/crds/crd-integration.yaml
+++ b/helm/camel-k/crds/crd-integration.yaml
@@ -6507,7 +6507,7 @@ spec:
in a csv format, ie, `<taskName1>,<taskName2>,...`. Mind
that you must include also the operator tasks (`builder`,
`quarkus-native`, `package`, `jib`, `spectrum`, `s2i`) if
- you need to execute them. Useful only wih `pod` strategy.
+ you need to execute them. Useful only with `pod` strategy.
type: string
tasksLimitCPU:
description: A list of limit cpu configuration for the specific
diff --git a/helm/camel-k/crds/crd-kamelet-binding.yaml b/helm/camel-k/crds/crd-kamelet-binding.yaml
index cc0b8e10e..6b119dfa4 100644
--- a/helm/camel-k/crds/crd-kamelet-binding.yaml
+++ b/helm/camel-k/crds/crd-kamelet-binding.yaml
@@ -6791,7 +6791,8 @@ spec:
in a csv format, ie, `<taskName1>,<taskName2>,...`.
Mind that you must include also the operator tasks (`builder`,
`quarkus-native`, `package`, `jib`, `spectrum`, `s2i`)
- if you need to execute them. Useful only wih `pod` strategy.
+ if you need to execute them. Useful only with `pod`
+ strategy.
type: string
tasksLimitCPU:
description: A list of limit cpu configuration for the
diff --git a/helm/camel-k/crds/crd-pipe.yaml b/helm/camel-k/crds/crd-pipe.yaml
index 35e8fdc8c..223dbb9fc 100644
--- a/helm/camel-k/crds/crd-pipe.yaml
+++ b/helm/camel-k/crds/crd-pipe.yaml
@@ -6789,7 +6789,8 @@ spec:
in a csv format, ie, `<taskName1>,<taskName2>,...`.
Mind that you must include also the operator tasks (`builder`,
`quarkus-native`, `package`, `jib`, `spectrum`, `s2i`)
- if you need to execute them. Useful only wih `pod` strategy.
+ if you need to execute them. Useful only with `pod`
+ strategy.
type: string
tasksLimitCPU:
description: A list of limit cpu configuration for the
diff --git a/resources/traits.yaml b/resources/traits.yaml
index a63e521e9..ddf942aeb 100755
--- a/resources/traits.yaml
+++ b/resources/traits.yaml
@@ -288,7 +288,7 @@ traits:
description: A list of tasks sorted by the order of execution in a csv format,
ie, `<taskName1>,<taskName2>,...`. Mind that you must include also the operator
tasks (`builder`, `quarkus-native`, `package`, `jib`, `spectrum`, `s2i`) if
- you need to execute them. Useful only wih `pod` strategy.
+ you need to execute them. Useful only with `pod` strategy.
- name: tasks-request-cpu
type: '[]string'
description: A list of request cpu configuration for the specific task with format
(camel-k) 01/02: doc: add languages section
Posted by pc...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
pcongiusti pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-k.git
commit 083a3b6ca5149a880c13080b09053a5e9519dd8e
Author: Pasquale Congiusti <pa...@gmail.com>
AuthorDate: Fri Jan 12 15:12:06 2024 +0100
doc: add languages section
Closes #5037
---
cmd/util/doc-gen/main.go | 2 +-
docs/antora.yml | 1 -
docs/modules/ROOT/nav-end.adoc | 97 --------
docs/modules/ROOT/nav.adoc | 105 +++++++++
docs/modules/ROOT/pages/languages/groovy.adoc | 194 ++++++++++++++++
docs/modules/ROOT/pages/languages/java.adoc | 25 ++
docs/modules/ROOT/pages/languages/javascript.adoc | 38 ++++
docs/modules/ROOT/pages/languages/jsh.adoc | 25 ++
docs/modules/ROOT/pages/languages/kotlin.adoc | 124 ++++++++++
docs/modules/ROOT/pages/languages/languages.adoc | 20 ++
docs/modules/ROOT/pages/languages/xml.adoc | 23 ++
docs/modules/ROOT/pages/languages/yaml.adoc | 263 ++++++++++++++++++++++
12 files changed, 818 insertions(+), 99 deletions(-)
diff --git a/cmd/util/doc-gen/main.go b/cmd/util/doc-gen/main.go
index d57036ce5..fdf2ecce1 100644
--- a/cmd/util/doc-gen/main.go
+++ b/cmd/util/doc-gen/main.go
@@ -35,7 +35,7 @@ func main() {
pflag.CommandLine.StringVar(&customArgs.DocDir, "doc-dir", "./docs", "Root of the document directory.")
pflag.CommandLine.StringVar(&customArgs.ResourceDir, "resource-dir", "./resources", "Root of the resource directory.")
pflag.CommandLine.StringVar(&customArgs.TraitPath, "traits-path", "modules/traits/pages", "Path to the traits directory.")
- pflag.CommandLine.StringVar(&customArgs.NavPath, "nav-path", "modules/ROOT/nav-end.adoc", "Path to the navigation file.")
+ pflag.CommandLine.StringVar(&customArgs.NavPath, "nav-path", "modules/ROOT/nav.adoc", "Path to the navigation file.")
pflag.CommandLine.StringVar(&customArgs.ListPath, "list-path", "modules/traits/pages/traits.adoc", "Path to the trait list file.")
arguments.CustomArgs = customArgs
diff --git a/docs/antora.yml b/docs/antora.yml
index bbc9fc5f6..e19fc0874 100644
--- a/docs/antora.yml
+++ b/docs/antora.yml
@@ -23,7 +23,6 @@ prerelease: true
display-version: Next (Pre-release)
nav:
- modules/ROOT/nav.adoc
- - modules/ROOT/nav-end.adoc
# It should be automatically generated by an action running nightly
asciidoc:
attributes:
diff --git a/docs/modules/ROOT/nav-end.adoc b/docs/modules/ROOT/nav-end.adoc
deleted file mode 100644
index 3f57cc06f..000000000
--- a/docs/modules/ROOT/nav-end.adoc
+++ /dev/null
@@ -1,97 +0,0 @@
-* xref:configuration/configuration.adoc[Configuration]
-** xref:configuration/build-time-properties.adoc[Build time properties]
-** xref:configuration/components.adoc[Components]
-** xref:configuration/dependencies.adoc[Dependencies]
-** xref:configuration/maven-profile.adoc[Maven Profile]
-** xref:configuration/runtime-properties.adoc[Properties]
-** xref:configuration/runtime-config.adoc[Runtime configuration]
-** xref:configuration/runtime-resources.adoc[Runtime resources]
-* xref:kamelets/kamelets.adoc[Kamelets]
-** xref:kamelets/kamelets-distribution.adoc[Distribution]
-** xref:kamelets/kamelets-user.adoc[User Guide]
-** xref:kamelets/kamelets-dev.adoc[Developer Guide]
-** xref:kamelets/kameletbindings-error-handler.adoc[Error Handling]
-* xref:traits:traits.adoc[Traits]
-// Start of autogenerated code - DO NOT EDIT! (trait-nav)
-** xref:traits:3scale.adoc[3Scale]
-** xref:traits:affinity.adoc[Affinity]
-** xref:traits:aws-secrets-manager.adoc[Aws Secrets Manager]
-** xref:traits:azure-key-vault.adoc[Azure Key Vault]
-** xref:traits:builder.adoc[Builder]
-** xref:traits:camel.adoc[Camel]
-** xref:traits:container.adoc[Container]
-** xref:traits:cron.adoc[Cron]
-** xref:traits:dependencies.adoc[Dependencies]
-** xref:traits:deployer.adoc[Deployer]
-** xref:traits:deployment.adoc[Deployment]
-** xref:traits:environment.adoc[Environment]
-** xref:traits:error-handler.adoc[Error Handler]
-** xref:traits:gc.adoc[Gc]
-** xref:traits:gcp-secret-manager.adoc[Gcp Secret Manager]
-** xref:traits:hashicorp-vault.adoc[Hashicorp Vault]
-** xref:traits:health.adoc[Health]
-** xref:traits:ingress.adoc[Ingress]
-** xref:traits:istio.adoc[Istio]
-** xref:traits:jolokia.adoc[Jolokia]
-** xref:traits:jvm.adoc[Jvm]
-** xref:traits:kamelets.adoc[Kamelets]
-** xref:traits:keda.adoc[Keda]
-** xref:traits:knative-service.adoc[Knative Service]
-** xref:traits:knative.adoc[Knative]
-** xref:traits:logging.adoc[Logging]
-** xref:traits:master.adoc[Master]
-** xref:traits:mount.adoc[Mount]
-** xref:traits:openapi.adoc[Openapi]
-** xref:traits:owner.adoc[Owner]
-** xref:traits:pdb.adoc[Pdb]
-** xref:traits:platform.adoc[Platform]
-** xref:traits:pod.adoc[Pod]
-** xref:traits:prometheus.adoc[Prometheus]
-** xref:traits:pull-secret.adoc[Pull Secret]
-** xref:traits:quarkus.adoc[Quarkus]
-** xref:traits:registry.adoc[Registry]
-** xref:traits:resume.adoc[Resume]
-** xref:traits:route.adoc[Route]
-** xref:traits:service-binding.adoc[Service Binding]
-** xref:traits:service.adoc[Service]
-** xref:traits:telemetry.adoc[Telemetry]
-** xref:traits:toleration.adoc[Toleration]
-** xref:traits:tracing.adoc[Tracing]
-// End of autogenerated code - DO NOT EDIT! (trait-nav)
-* xref:pipeline/pipeline.adoc[Pipelines]
-** xref:pipeline/tekton.adoc[Tekton]
-* Scaling
-** xref:scaling/integration.adoc[Integrations]
-** xref:scaling/binding.adoc[Pipes]
-* Observability
-** xref:observability/logging.adoc[Logging]
-*** xref:observability/logging/operator.adoc[Operator]
-*** xref:observability/logging/integration.adoc[Integration]
-** xref:observability/monitoring.adoc[Monitoring]
-*** xref:observability/monitoring/operator.adoc[Operator]
-*** xref:observability/monitoring/integration.adoc[Integration]
-* xref:troubleshooting/troubleshooting.adoc[Troubleshooting]
-** xref:troubleshooting/debugging.adoc[Debugging]
-** xref:troubleshooting/operating.adoc[Operating]
-** xref:troubleshooting/known-issues.adoc[Known Issues]
-* xref:architecture/architecture.adoc[Architecture]
-** xref:architecture/operator.adoc[Operator]
-*** xref:architecture/cr/integration-platform.adoc[IntegrationPlatform]
-*** xref:architecture/cr/integration.adoc[Integration]
-*** xref:architecture/cr/integration-kit.adoc[IntegrationKit]
-*** xref:architecture/cr/build.adoc[Build]
-*** xref:architecture/cr/camel-catalog.adoc[CamelCatalog]
-** xref:architecture/runtime.adoc[Runtime]
-** xref:architecture/traits.adoc[Traits]
-** xref:architecture/kamelets.adoc[Kamelets]
-** xref:architecture/incremental-image.adoc[Incremental Image]
-* API
-** xref:apis/camel-k.adoc[Camel K API]
-** xref:apis/kamelets.adoc[Kamelets API]
-** xref:apis/java.adoc[Java API]
-* xref:contributing/developers.adoc[Contributing]
-** xref:contributing/local-development.adoc[Local development]
-*** xref:contributing/local-execution.adoc[Operator - local execution]
-*** xref:contributing/remote-debugging.adoc[Operator - remote debug]
-** xref:contributing/local-deployment-olm.adoc[Local OLM deployment]
-** xref:contributing/e2e.adoc[Local E2E testing]
diff --git a/docs/modules/ROOT/nav.adoc b/docs/modules/ROOT/nav.adoc
index 20fb04f30..932121f8f 100644
--- a/docs/modules/ROOT/nav.adoc
+++ b/docs/modules/ROOT/nav.adoc
@@ -26,3 +26,108 @@
** xref:running/run-from-github.adoc[Run from GitHub]
** xref:running/promoting.adoc[Promote an Integration]
** xref:running/knative-sink.adoc[Knative Sinks]
+* xref:languages/languages.adoc[Languages]
+** xref:languages/java.adoc[Java]
+** xref:languages/yaml.adoc[YAML]
+** xref:languages/xml.adoc[XML]
+** xref:languages/groovy.adoc[Groovy]
+** xref:languages/javascript.adoc[Javascript]
+** xref:languages/jshell.adoc[JSheel]
+** xref:languages/kotlin.adoc[Kotlin]
+* xref:configuration/configuration.adoc[Configuration]
+** xref:configuration/build-time-properties.adoc[Build time properties]
+** xref:configuration/components.adoc[Components]
+** xref:configuration/dependencies.adoc[Dependencies]
+** xref:configuration/maven-profile.adoc[Maven Profile]
+** xref:configuration/runtime-properties.adoc[Properties]
+** xref:configuration/runtime-config.adoc[Runtime configuration]
+** xref:configuration/runtime-resources.adoc[Runtime resources]
+* xref:kamelets/kamelets.adoc[Kamelets]
+** xref:kamelets/kamelets-distribution.adoc[Distribution]
+** xref:kamelets/kamelets-user.adoc[User Guide]
+** xref:kamelets/kamelets-dev.adoc[Developer Guide]
+** xref:kamelets/kameletbindings-error-handler.adoc[Error Handling]
+* xref:traits:traits.adoc[Traits]
+// Start of autogenerated code - DO NOT EDIT! (trait-nav)
+** xref:traits:3scale.adoc[3Scale]
+** xref:traits:affinity.adoc[Affinity]
+** xref:traits:aws-secrets-manager.adoc[Aws Secrets Manager]
+** xref:traits:azure-key-vault.adoc[Azure Key Vault]
+** xref:traits:builder.adoc[Builder]
+** xref:traits:camel.adoc[Camel]
+** xref:traits:container.adoc[Container]
+** xref:traits:cron.adoc[Cron]
+** xref:traits:dependencies.adoc[Dependencies]
+** xref:traits:deployer.adoc[Deployer]
+** xref:traits:deployment.adoc[Deployment]
+** xref:traits:environment.adoc[Environment]
+** xref:traits:error-handler.adoc[Error Handler]
+** xref:traits:gc.adoc[Gc]
+** xref:traits:gcp-secret-manager.adoc[Gcp Secret Manager]
+** xref:traits:hashicorp-vault.adoc[Hashicorp Vault]
+** xref:traits:health.adoc[Health]
+** xref:traits:ingress.adoc[Ingress]
+** xref:traits:istio.adoc[Istio]
+** xref:traits:jolokia.adoc[Jolokia]
+** xref:traits:jvm.adoc[Jvm]
+** xref:traits:kamelets.adoc[Kamelets]
+** xref:traits:keda.adoc[Keda]
+** xref:traits:knative-service.adoc[Knative Service]
+** xref:traits:knative.adoc[Knative]
+** xref:traits:logging.adoc[Logging]
+** xref:traits:master.adoc[Master]
+** xref:traits:mount.adoc[Mount]
+** xref:traits:openapi.adoc[Openapi]
+** xref:traits:owner.adoc[Owner]
+** xref:traits:pdb.adoc[Pdb]
+** xref:traits:platform.adoc[Platform]
+** xref:traits:pod.adoc[Pod]
+** xref:traits:prometheus.adoc[Prometheus]
+** xref:traits:pull-secret.adoc[Pull Secret]
+** xref:traits:quarkus.adoc[Quarkus]
+** xref:traits:registry.adoc[Registry]
+** xref:traits:resume.adoc[Resume]
+** xref:traits:route.adoc[Route]
+** xref:traits:service-binding.adoc[Service Binding]
+** xref:traits:service.adoc[Service]
+** xref:traits:telemetry.adoc[Telemetry]
+** xref:traits:toleration.adoc[Toleration]
+** xref:traits:tracing.adoc[Tracing]
+// End of autogenerated code - DO NOT EDIT! (trait-nav)
+* xref:pipeline/pipeline.adoc[Pipelines]
+** xref:pipeline/tekton.adoc[Tekton]
+* Scaling
+** xref:scaling/integration.adoc[Integrations]
+** xref:scaling/binding.adoc[Pipes]
+* Observability
+** xref:observability/logging.adoc[Logging]
+*** xref:observability/logging/operator.adoc[Operator]
+*** xref:observability/logging/integration.adoc[Integration]
+** xref:observability/monitoring.adoc[Monitoring]
+*** xref:observability/monitoring/operator.adoc[Operator]
+*** xref:observability/monitoring/integration.adoc[Integration]
+* xref:troubleshooting/troubleshooting.adoc[Troubleshooting]
+** xref:troubleshooting/debugging.adoc[Debugging]
+** xref:troubleshooting/operating.adoc[Operating]
+** xref:troubleshooting/known-issues.adoc[Known Issues]
+* xref:architecture/architecture.adoc[Architecture]
+** xref:architecture/operator.adoc[Operator]
+*** xref:architecture/cr/integration-platform.adoc[IntegrationPlatform]
+*** xref:architecture/cr/integration.adoc[Integration]
+*** xref:architecture/cr/integration-kit.adoc[IntegrationKit]
+*** xref:architecture/cr/build.adoc[Build]
+*** xref:architecture/cr/camel-catalog.adoc[CamelCatalog]
+** xref:architecture/runtime.adoc[Runtime]
+** xref:architecture/traits.adoc[Traits]
+** xref:architecture/kamelets.adoc[Kamelets]
+** xref:architecture/incremental-image.adoc[Incremental Image]
+* API
+** xref:apis/camel-k.adoc[Camel K API]
+** xref:apis/kamelets.adoc[Kamelets API]
+** xref:apis/java.adoc[Java API]
+* xref:contributing/developers.adoc[Contributing]
+** xref:contributing/local-development.adoc[Local development]
+*** xref:contributing/local-execution.adoc[Operator - local execution]
+*** xref:contributing/remote-debugging.adoc[Operator - remote debug]
+** xref:contributing/local-deployment-olm.adoc[Local OLM deployment]
+** xref:contributing/e2e.adoc[Local E2E testing]
diff --git a/docs/modules/ROOT/pages/languages/groovy.adoc b/docs/modules/ROOT/pages/languages/groovy.adoc
new file mode 100644
index 000000000..ac8f56849
--- /dev/null
+++ b/docs/modules/ROOT/pages/languages/groovy.adoc
@@ -0,0 +1,194 @@
+= Writing Integrations in Groovy
+
+[WARNING]
+====
+The Groovy DSL is experimental.
+====
+
+An integration written in Groovy looks very similar to a Java one except it can leverages Groovy's language enhancements over Java such as closures:
+
+[source,groovy]
+----
+from('timer:tick')
+ .process { it.in.body = 'Hello Camel K!' }
+ .to('log:info')
+----
+
+You can run it with the standard command:
+
+```
+kamel run example.groovy
+```
+
+== Configuring the Application
+
+Camel K extends the Camel Java DSL making it easier to configure Camel's behavior using the top level _camel_ block
+
+[source,groovy]
+----
+camel {
+ // configure camel here
+}
+----
+
+The _camel_ block allows to configure the following Camel features:
+
+- **Components**
++
+[source,groovy]
+----
+camel {
+ components {
+ seda { // <1>
+ queueSize = 1234
+ concurrentConsumers = 12
+ }
+
+ log { // <2>
+ exchangeFormatter = {
+ 'body ==> ' + it.in.body
+ } as org.apache.camel.spi.ExchangeFormatter
+ }
+
+ mySeda(SedaComponent) { // <3>
+ queueSize = 4321
+ concurrentConsumers = 21
+ }
+ }
+}
+----
+<1> configure the properties of the component whit name _seda_
+<2> configure the properties of the component whit name _log_
+<3> creates and configure a component of type `SedaComponent` whose name is _mySeda_
++
+Setting the property _exchangeFormatter_ looks a little ugly as you have to declare the type of your closure. For demonstration purpose, we have created a Groovy extension module that simplifies configuring the _exchangeFormatter_ so you can rewrite your DSL as
++
+[source,groovy]
+----
+camel {
+ components {
+ log {
+ formatter {
+ 'body ==> ' + it.in.body
+ }
+ }
+ }
+}
+----
++
+which is much better.
++
+[TIP]
+====
+You can provide your custom extensions by packaging them in a dependency you declare for your integration.
+====
+
+- **Languages **
++
+[source,groovy]
+----
+camel {
+ languages {
+ language("bean") { // <1>
+ beanType = String.class
+ method = "toUpperCase"
+ }
+ myBean(BeanLanguage) { // <2>
+ beanType = String.class
+ method = "toLowerCase"
+ }
+ simple { // <3>
+ }
+ }
+}
+----
+<1> configure the properties of the language whit name _bean_
+<2> creates and configure a language of type `BeanLanguage` whose name is _myBean_
+<3> configure the properties of the language whit name _simple_
+
+- **DataFormats**
++
+[source,groovy]
+----
+camel {
+ dataFormats {
+ dataFormat("json-jackson") { // <1>
+ unmarshalType = Map.class
+ prettyPrint = true
+ }
+ myJackson(JacksonDataFormat) { // <2>
+ unmarshalType = String.class
+ prettyPrint = false
+ }
+ csv { // <3>
+ }
+ }
+}
+----
+<1> configure the properties of the data format whit name _json-jackson_
+<2> creates and configure a data format of type `JacksonDataFormat` whose name is _myJackson_
+<3> configure the properties of the data format whit name _csv_
+
+
+== Beans
+
+Beans can be bound to the _registry_ using a dedicated _bean DSL_ :
+
+[source,groovy]
+----
+beans {
+ myCache = Caffeine.newBuilder().build() // <1>
+
+ myProcessor = processor { // <2>
+ it.in.body = 'Hello Camel K!'
+ }
+
+ myPredicate = predicate { // <3>
+ it.in.body != null
+ }
+
+ dataSource(org.apache.commons.dbcp2.BasicDataSource) { //<4>
+ driverClassName = "org.h2.Driver"
+ url = "jdbc:h2:mem:camel"
+ username = "sa"
+ password = ""
+ }
+}
+----
+<1> define a bean
+<2> define a custom processor
+<3> define a custom predicate
+<4> define a custom bean with name `dataSource` and type `org.apache.commons.dbcp2.BasicDataSource`
+
+
+== Rest Support
+
+Integrations REST endpoints can be configured using the top level _rest_ block:
+
+[source,groovy]
+----
+rest {
+ configuration { // <1>
+ host = 'my-host'
+ port '9192'
+ }
+
+ path('/my/path') {
+ get('/get') { // <2>
+ consumes 'application/json'
+ produces 'application/json'
+ to 'direct:get'
+ }
+ }
+
+ post { // <3>
+ path '/post'
+ consumes 'application/json'
+ produces 'application/json'
+ to 'direct:post'
+ }
+}
+----
+<1> Configure the rest engine
+<2> Configure the behavior of the method GET for the path '/my/path/get' and invoke the endpoint 'direct:get'
+<3> Configure the behavior of the method POST for the path '/post' and invoke the endpoint 'direct:post'
diff --git a/docs/modules/ROOT/pages/languages/java.adoc b/docs/modules/ROOT/pages/languages/java.adoc
new file mode 100644
index 000000000..d97585222
--- /dev/null
+++ b/docs/modules/ROOT/pages/languages/java.adoc
@@ -0,0 +1,25 @@
+= Writing Integrations in Java
+
+Using Java to write an integration to be deployed using Camel K is no different from defining your routing rules in Camel with the only difference that you do not need to build and package it as a jar.
+
+[source,java]
+.Example.java
+----
+import org.apache.camel.builder.RouteBuilder;
+
+public class Example extends RouteBuilder {
+ @Override
+ public void configure() throws Exception {
+ from("timer:tick")
+ .setBody()
+ .constant("Hello Camel K!")
+ .to("log:info");
+ }
+}
+----
+
+You can run it with the standard command:
+
+```
+kamel run Example.java
+```
diff --git a/docs/modules/ROOT/pages/languages/javascript.adoc b/docs/modules/ROOT/pages/languages/javascript.adoc
new file mode 100644
index 000000000..6ea5b8b70
--- /dev/null
+++ b/docs/modules/ROOT/pages/languages/javascript.adoc
@@ -0,0 +1,38 @@
+= Writing Integrations in JavaScript
+
+[WARNING]
+====
+The JavaScript DSL is experimental.
+====
+
+An integration written in JavaScript looks very similar to a Java one:
+
+[source,js]
+.hello.js
+----
+function proc(e) {
+ e.getIn().setBody('Hello Camel K!')
+}
+
+from('timer:tick')
+ .process(proc)
+ .to('log:info')
+----
+
+To run it, you need just to execute:
+
+```
+kamel run hello.js
+```
+
+For JavaScript integrations, Camel K does not yet provide an enhanced DSL, but you can access to some global bounded objects such as a writable registry and the camel context so to set the property _exchangeFormatter_ of the _LogComponent_ as done in previous example, you can do something like:
+
+[source,js]
+----
+
+l = context.getComponent('log', true, false)
+l.exchangeFormatter = function(e) {
+ return "log - body=" + e.in.body + ", headers=" + e.in.headers
+}
+----
+
diff --git a/docs/modules/ROOT/pages/languages/jsh.adoc b/docs/modules/ROOT/pages/languages/jsh.adoc
new file mode 100644
index 000000000..1de6a1428
--- /dev/null
+++ b/docs/modules/ROOT/pages/languages/jsh.adoc
@@ -0,0 +1,25 @@
+= Writing Integrations in Java
+
+[WARNING]
+====
+The JShell DSL is experimental.
+====
+
+Using Java and JShell to write an integration to be deployed using Camel K is no different from defining your routing rules in Camel with the only difference that you do not need to implement or extend a RouteBuilder but you can access the current builder thx to the built-in `builder` variable.
+
+[source,java]
+.example.jsh
+----
+builder.from("timer:tick")
+ .setBody()
+ .constant("Hello Camel K!")
+ .to("log:info");-
+----
+
+You can run it with the standard command:
+
+```
+kamel run example.jsh
+```
+
+
diff --git a/docs/modules/ROOT/pages/languages/kotlin.adoc b/docs/modules/ROOT/pages/languages/kotlin.adoc
new file mode 100644
index 000000000..697b68760
--- /dev/null
+++ b/docs/modules/ROOT/pages/languages/kotlin.adoc
@@ -0,0 +1,124 @@
+= Writing Integrations in Kotlin
+
+[WARNING]
+====
+The Kotlin DSL is experimental.
+====
+
+An integration written in Kotlin looks very similar to a Java one except it can leverages Kotlin's language enhancements over Java:
+
+[source,kotlin]
+----
+from("timer:tick")
+ .process { e -> e.getIn().body = "Hello Camel K!" }
+ .to("log:info")
+----
+
+You can run it with the standard command:
+
+```
+kamel run example.kts
+```
+
+Camel K extends the Camel Java DSL making it easier to configure the context in which the integration runs using the top level _context_ block
+
+[source,kotlin]
+----
+context {
+ // configure the context here
+}
+----
+
+At the moment, the enhanced DSL provides a way to bind items to the registry, to configure the components the context creates and some improvements over the REST DSL.
+
+== Beans DSL
+
+To register beans as you would do with a Camel registry you can use the Beans DSL
+
+[source,kotlin]
+----
+beans {
+ bean<org.apache.commons.dbcp2.BasicDataSource>("dataSource") { <1>
+ driverClassName = "org.h2.Driver"
+ url = "jdbc:h2:mem:camel"
+ username = "sa"
+ password = ""
+ }
+
+ bean("filterStrategy") { <1>
+ org.apache.camel.support.DefaultHeaderFilterStrategy()
+ }
+
+ processor("myProcessor") { <2>
+ it.getIn().body = "Hello"
+ }
+
+ predicate("myPredicate") { <3>
+ false
+ }
+}
+----
+<1> bind beans to the context for the database and filter strategy
+<2> define a custom processor to be used later in the routes by ref
+<3> define a custom predicate to be used later in the routes by ref
+
+
+== Components Configuration
+
+Components can be configured within the _components_ block inside the _camel_ one:
+
+[source,kotlin]
+----
+camel {
+ components {
+
+ component<SedaComponent>("seda") { //<1>
+ queueSize = 1234
+ concurrentConsumers = 12
+ }
+
+ component<SedaComponent>("mySeda") { // <2>
+ queueSize = 4321
+ concurrentConsumers = 21
+ }
+
+ component<LogComponent>("log") { // <3>
+ setExchangeFormatter {
+ e: Exchange -> "" + e.getIn().body
+ }
+ }
+ }
+}
+----
+<1> configure the properties of a component whit type _SedaComponent_ and name _seda_
+<2> configure the properties of a component with type SedaComponent and name _mySeda_, note that as _mySeda_ does not represent a valid component scheme, a new component of the required type will be instantiated.
+<3> configure the properties of the component whit name _log_
+
+[NOTE]
+====
+As for Groovy, you can provide your custom extension to the DSL
+====
+
+== Rest Endpoints
+
+Integrations REST endpoints can be configured using the top level _rest_ block:
+
+[source,kotlin]
+----
+rest {
+ configuration { // <1>
+ host = "my-host"
+ port = "9192"
+ }
+
+ path("/my/path") { // <2>
+ get("/get") {
+ consumes("application/json")
+ produces("application/json")
+ to("direct:get")
+ }
+ }
+}
+----
+<1> Configure the rest engine
+<2> Configure the rest endpoint for the base path '/my/path'
diff --git a/docs/modules/ROOT/pages/languages/languages.adoc b/docs/modules/ROOT/pages/languages/languages.adoc
new file mode 100644
index 000000000..7f132fcb8
--- /dev/null
+++ b/docs/modules/ROOT/pages/languages/languages.adoc
@@ -0,0 +1,20 @@
+[[languages]]
+= Languages
+
+Camel K supports multiple languages for writing integrations:
+
+.Supported Languages
+[options="header"]
+[cols="30%,70%"]
+|=======================
+| Language | Description
+| xref:java.adoc[Java] | Integrations written in Java DSL are supported
+| xref:xml.adoc[XML] | Integrations written in plain XML DSL are supported (Spring XML with <beans> or Blueprint XML with <blueprint> not supported)
+| xref:yaml.adoc[YAML] | Integrations written in YAML DSL are supported
+| xref:groovy.adoc[Groovy] | Groovy `.groovy` files are supported (experimental)
+| xref:kotlin.adoc[Kotlin] | Kotlin Script `.kts` files are supported (experimental)
+| xref:jsh.adoc[JShell] | JShell (Java Shell) `.jsh` files are supported (experimental)
+| xref:javascript.adoc[JavaScript] | JavaScript `.js` files are supported (experimental)
+|=======================
+
+More information about each language is located in the language specific sections. Mind that the compatibility of each DSL with Camel will depend on the runtime you'll use to run the Integration.
diff --git a/docs/modules/ROOT/pages/languages/xml.adoc b/docs/modules/ROOT/pages/languages/xml.adoc
new file mode 100644
index 000000000..c03876c59
--- /dev/null
+++ b/docs/modules/ROOT/pages/languages/xml.adoc
@@ -0,0 +1,23 @@
+= Writing Integrations in XML
+
+Camel K support the classic XML DSL available in Camel:
+
+[source,xml]
+.example.xml
+----
+<routes xmlns="http://camel.apache.org/schema/spring">
+ <route>
+ <from uri="timer:tick"/>
+ <setBody>
+ <constant>Hello Camel K!</constant>
+ </setBody>
+ <to uri="log:info"/>
+ </route>
+</routes>
+----
+
+You can run it by executing:
+
+```
+kamel run example.xml
+```
diff --git a/docs/modules/ROOT/pages/languages/yaml.adoc b/docs/modules/ROOT/pages/languages/yaml.adoc
new file mode 100644
index 000000000..709e2efb3
--- /dev/null
+++ b/docs/modules/ROOT/pages/languages/yaml.adoc
@@ -0,0 +1,263 @@
+= Writing Integrations in YAML
+
+== Defining a route
+
+A route is collection of elements defined as follows:
+
+[source,yaml]
+----
+- from: #<1>
+ uri: "direct:start"
+ steps: #<2>
+ - filter:
+ expression:
+ simple: "${in.header.continue} == true"
+ steps: #<2>
+ - to:
+ uri: "log:filtered"
+ - to:
+ uri: "log:original"
+----
+<1> route entry point, by default `from` and `rest` are supported
+<2> processing steps
+
+[NOTE]
+====
+Each step is represented by a YAML map that has a single entry where the field name is the EIP name
+====
+
+As general rule each step provide all the parameters the related definition declares but there are some minor differences/enhancements:
+
+- *Output Aware Steps*
++
+Some steps such as `filter` and `split` have their own pipeline when an exchange matches the filter expression or for the items generated by the split expression, such pipeline can be defined by the `steps` field:
++
+[source,yaml]
+----
+filter:
+ expression:
+ simple: "${in.header.continue} == true"
+ steps:
+ - to:
+ uri: "log:filtered"
+----
++
+[NOTE]
+====
+if the `steps` field is omitted, then each subsequent step is considered part of the filter pipeline.
+====
+
+- *Expression Aware Steps*
++
+Some EIP such as `filter` and `split` supports the definition of an expression through the `expression` field:
++
+[source,yaml]
+.Explicit Expression field
+----
+filter:
+ expression:
+ simple: "${in.header.continue} == true"
+----
++
+To make the DSL less verbose, the `expression` field can be omitted:
++
+[source,yaml]
+.Implicit Expression field
+----
+filter:
+ simple: "${in.header.continue} == true"
+----
++
+In general expression can be defined inline like in the examples above but in case you need provide more information, you can 'unroll' the expression definition and configure any single parameter the expression defines.
++
+[source,yaml]
+.Full Expression definition
+----
+filter:
+ tokenize:
+ token: "<"
+ end-token: ">"
+----
+
+- *Data Format Aware Steps*
++
+Some EIP such as `set-body` and `marshal` supports the definition of data formats through the `data-format` field:
++
+[source,yaml]
+.Explicit Data Format field
+----
+set-body:
+ data-format:
+ json:
+ library: Gson
+----
++
+To make the DSL less verbose, the `data-format` field can be omitted:
++
+[source,yaml]
+.Implicit Data Format field
+----
+set-body:
+ json:
+ library: Gson
+----
++
+[NOTE]
+====
+In case you want to use the data-format's default settings, you need to place an empty block as data format parameters, like `json: {}`
+====
+
+== Defining endpoints
+
+To define an endpoint with the YAML dsl you have three options:
+
+. Using a classic Camel URI:
++
+[source,yaml]
+----
+- from:
+ uri: "timer:tick?period=1s"
+ steps:
+ - to:
+ uri: "telegram:bots?authorizationToken=XXX"
+----
+. Using URI and parameters:
++
+[source,yaml]
+----
+- from:
+ uri: "timer://tick"
+ parameters:
+ period: "1s"
+ steps:
+ - to:
+ uri: "telegram:bots"
+ parameters:
+ authorizationToken: "XXX"
+----
+. Using the YAML implementation of the xref:manual::Endpoint-dsl.adoc[Endpoint DSL]:
++
+[source,yaml]
+----
+- from:
+ timer:
+ name: "tick"
+ period: "1s"
+ steps:
+ - telegram:
+ type: "bots"
+ authorizationToken: "XXX"
+----
+
+[WARNING]
+====
+Support for the Endpoint DSL with YAML is experimental and subject to changes.
+====
+[NOTE]
+====
+Support for Endpoint DSL auto completion https://github.com/apache/camel-k-runtime/issues/485[is not yet available].
+====
+
+== Defining beans
+
+In addition to the general support for creating beans provided by xref:{camel-docs-version}@components:others:main.adoc#_specifying_custom_beans[Camel Main], the YAML DSL provide a convenient syntax to define and configure them:
+
+[source,yaml]
+----
+- beans:
+ - name: beanFromMap # <1>
+ type: com.acme.MyBean # <2>
+ properties: # <3>
+ foo: bar
+----
+<1> the name of the bean which will be used to bound the instance to the Camel Registry
+<2> the full qualified class name of the bean
+<3> the properties of the bean to be set
+
+The properties of the bean can be defined using either a map or properties style as shown in the example below:
+
+[source,yaml]
+----
+- beans:
+ # map style
+ - name: beanFromMap
+ type: com.acme.MyBean
+ properties:
+ field1: 'f1'
+ field2: 'f2'
+ nested:
+ field1: 'nf1'
+ field2: 'nf2'
+ # properties style
+ - name: beanFromProps
+ type: com.acme.MyBean
+ properties:
+ field1: 'f1_p'
+ field2: 'f2_p'
+ nested.field1: 'nf1_p'
+ nested.field2: 'nf2_p'
+----
+
+[NOTE]
+====
+The `beans` elements can only be used as root element
+====
+
+== Supported EIP
+
+This is the list of EIPs supported in the yaml DSL language. For full details on expected configuration you can please refer to the https://github.com/apache/camel/blob/main/dsl/camel-yaml-dsl/camel-yaml-dsl/src/generated/resources/schema/camel-yaml-dsl.json[YAML language specification].
+
+- Aggregate
+- Bean
+- Choice
+- Circuit Breaker
+- Claim Check
+- Convert Body To
+- Delay
+- Dynamic Router
+- Enrich
+- Filter
+- From
+- Idempotent Consumer
+- Load Balance
+- Log
+- Loop
+- Marshal
+- Multicast
+- Pipeline
+- PollEnrich
+- Process
+- Recipient List
+- Remove Header
+- Remove Headers
+- Remove Property
+- Remove Properties
+- Resequence
+- Rest DSL
+- Rollback
+- Routing Slip
+- Saga
+- Sample
+- Script
+- ServiceCall
+- Set Body
+- Set Exchange Pattern
+- Set Header
+- Set Property
+- Sort
+- Split
+- Step
+- Stop
+- Threads
+- Throttle
+- Throw Exception
+- To
+- To Dynamic
+- Transacted
+- Transform
+- Try Catch Finally
+- Unmarshal
+- Validate
+- Wire Tap
+
+The Try Catch Finally EIP currently only support specifying one `do-catch` clause.