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 a7787de7d chore: default data types on the DNS, geocoding and SSH
Kamelets where the body is fixed (#3117) (#3278)
a7787de7d is described below
commit a7787de7db9b121ab5bd6db596644a6989440682
Author: Claus Ibsen <[email protected]>
AuthorDate: Thu Nov 19 18:32:28 2026 +0100
chore: default data types on the DNS, geocoding and SSH Kamelets where the
body is fixed (#3117) (#3278)
dns-dig-action and dns-ip-action give text (text-plain); dns-lookup-action
and
nominatim-geocode-action give their JSON array as bytes (application-json);
ssh-sink takes its command as text (text-plain). The Citrus tests of #3264
and
#3271 expect the new body type and Content-Type.
Co-authored-by: Claude Opus 5.5 <[email protected]>
---
kamelets/dns-dig-action.kamelet.yaml | 9 ++++++++-
kamelets/dns-ip-action.kamelet.yaml | 9 ++++++++-
kamelets/dns-lookup-action.kamelet.yaml | 9 ++++++++-
kamelets/nominatim-geocode-action.kamelet.yaml | 8 +++++++-
kamelets/ssh-sink.kamelet.yaml | 9 ++++++++-
.../src/main/resources/META-INF/kamelets-index.json | 10 +++++-----
.../src/main/resources/kamelets/dns-dig-action.kamelet.yaml | 9 ++++++++-
.../src/main/resources/kamelets/dns-ip-action.kamelet.yaml | 9 ++++++++-
.../src/main/resources/kamelets/dns-lookup-action.kamelet.yaml | 9 ++++++++-
.../resources/kamelets/nominatim-geocode-action.kamelet.yaml | 8 +++++++-
.../src/main/resources/kamelets/ssh-sink.kamelet.yaml | 9 ++++++++-
.../src/test/resources/dns/dns-dig-action-route.citrus.it.yaml | 2 +-
.../geo/nominatim-geocode-action-route.citrus.it.yaml | 2 +-
.../src/test/resources/ssh/ssh-sink-route.citrus.it.yaml | 2 +-
14 files changed, 86 insertions(+), 18 deletions(-)
diff --git a/kamelets/dns-dig-action.kamelet.yaml
b/kamelets/dns-dig-action.kamelet.yaml
index 16b0c7557..cece64287 100644
--- a/kamelets/dns-dig-action.kamelet.yaml
+++ b/kamelets/dns-dig-action.kamelet.yaml
@@ -37,7 +37,7 @@ spec:
Input: the name to look up, taken from the `domain-name` header, else
from the `ce-domainname` header, else from the body as text. The kind of record
comes from the `dns-type` header, else from the `ce-dnstype` header, else it is
`A` (the IPv4 addresses).
- Output: the body is the whole answer as text, as the `dig` command shows
it: the question, the records found, and the status, such as `NOERROR`.
+ Output: the body is the whole answer as text, as the `dig` command shows
it: the question, the records found, and the status, such as `NOERROR`. The
`Content-Type` header is set to `text/plain`.
Good to know: a name the DNS does not know does not fail the message:
the answer has the status `NXDOMAIN` and no records. The Kamelet has no
options; it asks the DNS servers of the machine it runs on. Headers that start
with `CamelDns` are removed from the message first, so they cannot change what
the Kamelet does.
type: object
@@ -60,6 +60,13 @@ spec:
title: Record Type (CloudEvents)
description: "The kind of record to ask for, when the message is a
CloudEvent. Used only when `dns-type` is not set."
type: string
+ out:
+ default: text
+ types:
+ text:
+ format: "text-plain"
+ description: "The answer, as the text that the dig command shows."
+ mediaType: text/plain
dependencies:
- "camel:dns"
- "camel:kamelet"
diff --git a/kamelets/dns-ip-action.kamelet.yaml
b/kamelets/dns-ip-action.kamelet.yaml
index a80dd0187..ee59dc05e 100644
--- a/kamelets/dns-ip-action.kamelet.yaml
+++ b/kamelets/dns-ip-action.kamelet.yaml
@@ -38,7 +38,7 @@ spec:
Input: the name to look up, taken from the `domain` header, else from
the `ce-domain` header, else from the body as text.
- Output: the body is one IP address, as text, such as `151.101.2.132`.
+ Output: the body is one IP address, as text, such as `151.101.2.132`,
and the `Content-Type` header is set to `text/plain`.
Good to know: when a name has several addresses, only one of them is
given. A name the DNS does not know fails the message with an unknown host
error. The headers are `domain` and `ce-domain`, not `domain-name` as for
`dns-lookup-action` and `dns-dig-action`. The Kamelet has no options; it uses
the name resolution of the machine it runs on. Headers that start with
`CamelDns` are removed from the message first, so they cannot change what the
Kamelet does.
type: object
@@ -53,6 +53,13 @@ spec:
title: Domain (CloudEvents)
description: "The host name to look up, when the message is a
CloudEvent. Used only when `domain` is not set."
type: string
+ out:
+ default: text
+ types:
+ text:
+ format: "text-plain"
+ description: "The IP address, as text."
+ mediaType: text/plain
dependencies:
- "camel:dns"
- "camel:kamelet"
diff --git a/kamelets/dns-lookup-action.kamelet.yaml
b/kamelets/dns-lookup-action.kamelet.yaml
index 51aad73df..7f3f564e3 100644
--- a/kamelets/dns-lookup-action.kamelet.yaml
+++ b/kamelets/dns-lookup-action.kamelet.yaml
@@ -37,7 +37,7 @@ spec:
Input: the name to look up, taken from the `domain-name` header, else
from the `ce-domainname` header, else from the body as text.
- Output: the body is a JSON array with one entry per record found. Each
entry has the type, the class and the time to live of the record.
+ Output: the body is a JSON array, as bytes, with one entry per record
found, and the `Content-Type` header is set to `application/json`. Each entry
has the type, the class and the time to live of the record.
Good to know: a name the DNS does not know fails the message with "host
not found". The Kamelet has no options; it asks the DNS servers of the machine
it runs on. Headers that start with `CamelDns` are removed from the message
first, so they cannot change what the Kamelet does.
type: object
@@ -55,6 +55,13 @@ spec:
title: Domain Name (CloudEvents)
description: The host name to look up, when the message is a
CloudEvent. Used only when `domain-name` is not set.
type: string
+ out:
+ default: json
+ types:
+ json:
+ format: "application-json"
+ description: "The records found, as a JSON array in bytes."
+ mediaType: application/json
dependencies:
- "camel:jackson3"
- "camel:dns"
diff --git a/kamelets/nominatim-geocode-action.kamelet.yaml
b/kamelets/nominatim-geocode-action.kamelet.yaml
index 2dbca5824..d1536ef86 100644
--- a/kamelets/nominatim-geocode-action.kamelet.yaml
+++ b/kamelets/nominatim-geocode-action.kamelet.yaml
@@ -37,7 +37,7 @@ spec:
Input: the place name or address to look up, as text.
- Output: the body is JSON text: an array with the best match, with its
coordinates, its full address and its kind of place, or an empty array when
nothing matches. The headers give the same answer in short: `CamelGeoCoderLat`
and `CamelGeoCoderLng` (the coordinates), `CamelGeoCoderAddress` (the full
address found), `CamelGeoCoderCity`, `CamelGeoCoderCountryLong`,
`CamelGeoCoderPostalCode` and `CamelGeoCoderStatus`, which is `OK` when a place
was found and `ZERO_RESULTS` when none was.
+ Output: the body is JSON text, as bytes, with `Content-Type:
application/json`: an array with the best match, with its coordinates, its full
address and its kind of place, or an empty array when nothing matches. The
headers give the same answer in short: `CamelGeoCoderLat` and
`CamelGeoCoderLng` (the coordinates), `CamelGeoCoderAddress` (the full address
found), `CamelGeoCoderCity`, `CamelGeoCoderCountryLong`,
`CamelGeoCoderPostalCode` and `CamelGeoCoderStatus`, which is `OK` when [...]
Good to know: a place that is not found does not fail the message; check
`CamelGeoCoderStatus`. The public server `https://nominatim.openstreetmap.org`
limits how often it may be called; for many lookups, run your own Nominatim
server. Headers that start with `CamelGeoCoder` are removed from the message
first, so they cannot change what the Kamelet does.
required:
@@ -51,6 +51,7 @@ spec:
type: string
dataTypes:
out:
+ default: json
headers:
CamelGeoCoderStatus:
title: Status
@@ -88,6 +89,11 @@ spec:
title: Postal Code
description: The postal code of the place found.
type: string
+ types:
+ json:
+ format: "application-json"
+ description: "The best match, as a JSON array in bytes."
+ mediaType: application/json
types:
in:
mediaType: text/plain
diff --git a/kamelets/ssh-sink.kamelet.yaml b/kamelets/ssh-sink.kamelet.yaml
index caff37f1e..49ca36a5a 100644
--- a/kamelets/ssh-sink.kamelet.yaml
+++ b/kamelets/ssh-sink.kamelet.yaml
@@ -37,7 +37,7 @@ spec:
Input: the body is the command to run, as text, such as `systemctl
restart myapp`. It runs in the shell of `username`, so it can hold several
commands separated by `;`.
- Output: the body afterwards is what the command printed on its standard
output, as a stream. The `CamelSshExitValue` header holds the exit code of the
command, and `CamelSshStderr` what it printed on its standard error, as a
stream.
+ Output: the body afterwards is what the command printed on its standard
output, as a stream, and the `Content-Type` header is `text/plain`. The
`CamelSshExitValue` header holds the exit code of the command, and
`CamelSshStderr` what it printed on its standard error, as a stream.
Good to know: it runs whatever command it receives, with the rights of
`username`. Never send it messages from an untrusted source, and log in with an
account that may do only what is needed. A command that ends with an exit code
other than 0 does not fail the message: check `CamelSshExitValue`. Log in with
`password`, or with a private key in `privateKeyResource` when the server does
not take passwords; when a key is set, the password is not used. The key of the
server is checked [...]
required:
@@ -103,6 +103,13 @@ spec:
out:
mediaType: text/plain
dataTypes:
+ in:
+ default: text
+ types:
+ text:
+ format: "text-plain"
+ description: "The command to run, as text."
+ mediaType: text/plain
out:
headers:
CamelSshExitValue:
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 1e54d7133..4feef01c6 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
@@ -645,7 +645,7 @@
"supportLevel" : "Stable",
"title" : "DNS DIG Action",
"summary" : "Asks the DNS for the records of one kind, such as A or MX, of
a name, and gives the answer as text, in the format of the `dig` tool.",
- "description" : "Asks the DNS for the records of one kind, such as A or
MX, of a name, and gives the answer as text, in the format of the `dig`
tool.\n\nUse it to see the records of a domain, such as its mail (MX) records,
for example to check a DNS change. To get only the IP address of a name, use
`dns-ip-action`, and to get its address records as JSON, use
`dns-lookup-action`.\n\nInput: the name to look up, taken from the
`domain-name` header, else from the `ce-domainname` header, [...]
+ "description" : "Asks the DNS for the records of one kind, such as A or
MX, of a name, and gives the answer as text, in the format of the `dig`
tool.\n\nUse it to see the records of a domain, such as its mail (MX) records,
for example to check a DNS change. To get only the IP address of a name, use
`dns-ip-action`, and to get its address records as JSON, use
`dns-lookup-action`.\n\nInput: the name to look up, taken from the
`domain-name` header, else from the `ce-domainname` header, [...]
"group" : "DNS",
"namespace" : "Networking",
"provider" : "Apache Software Foundation"
@@ -655,7 +655,7 @@
"supportLevel" : "Stable",
"title" : "DNS IP Action",
"summary" : "Finds the IP address of a host name, such as `apache.org`,
and gives it as text.",
- "description" : "Finds the IP address of a host name, such as
`apache.org`, and gives it as text.\n\nUse it to turn a host name into an
address for a later step, or to check that a name can be resolved. To see all
the address records of a name with how long they may be cached, use
`dns-lookup-action`, and to ask for other kinds of record, such as mail (MX)
records, use `dns-dig-action`.\n\nInput: the name to look up, taken from the
`domain` header, else from the `ce-domain` header, e [...]
+ "description" : "Finds the IP address of a host name, such as
`apache.org`, and gives it as text.\n\nUse it to turn a host name into an
address for a later step, or to check that a name can be resolved. To see all
the address records of a name with how long they may be cached, use
`dns-lookup-action`, and to ask for other kinds of record, such as mail (MX)
records, use `dns-dig-action`.\n\nInput: the name to look up, taken from the
`domain` header, else from the `ce-domain` header, e [...]
"group" : "DNS",
"namespace" : "Networking",
"provider" : "Apache Software Foundation"
@@ -665,7 +665,7 @@
"supportLevel" : "Stable",
"title" : "DNS Lookup Action",
"summary" : "Asks the DNS for the address records of a host name, such as
`apache.org`, and gives them as JSON.",
- "description" : "Asks the DNS for the address records of a host name, such
as `apache.org`, and gives them as JSON.\n\nUse it to check that a name exists
in the DNS, or to see its records and how long they may be cached, for example
to monitor a domain. To get the IP address of a name, use `dns-ip-action`
instead, and to ask for other kinds of record, such as mail (MX) records, use
`dns-dig-action`.\n\nInput: the name to look up, taken from the `domain-name`
header, else from the `ce [...]
+ "description" : "Asks the DNS for the address records of a host name, such
as `apache.org`, and gives them as JSON.\n\nUse it to check that a name exists
in the DNS, or to see its records and how long they may be cached, for example
to monitor a domain. To get the IP address of a name, use `dns-ip-action`
instead, and to ask for other kinds of record, such as mail (MX) records, use
`dns-dig-action`.\n\nInput: the name to look up, taken from the `domain-name`
header, else from the `ce [...]
"group" : "DNS",
"namespace" : "Networking",
"provider" : "Apache Software Foundation"
@@ -1595,7 +1595,7 @@
"supportLevel" : "Stable",
"title" : "Nominatim GeoCode Action",
"summary" : "Looks up a place name or a postal address, such as `Eiffel
Tower, Paris`, in a Nominatim server of OpenStreetMap, and gives the best match
with its coordinates as JSON.",
- "description" : "Looks up a place name or a postal address, such as
`Eiffel Tower, Paris`, in a Nominatim server of OpenStreetMap, and gives the
best match with its coordinates as JSON.\n\nUse it to turn the addresses in
orders, customer records or events into latitude and longitude, for example to
show them on a map or to find the nearest store.\n\nInput: the place name or
address to look up, as text.\n\nOutput: the body is JSON text: an array with
the best match, with its coordinat [...]
+ "description" : "Looks up a place name or a postal address, such as
`Eiffel Tower, Paris`, in a Nominatim server of OpenStreetMap, and gives the
best match with its coordinates as JSON.\n\nUse it to turn the addresses in
orders, customer records or events into latitude and longitude, for example to
show them on a map or to find the nearest store.\n\nInput: the place name or
address to look up, as text.\n\nOutput: the body is JSON text, as bytes, with
`Content-Type: application/json`: [...]
"group" : "Geospatial",
"namespace" : "Geo",
"provider" : "Apache Software Foundation"
@@ -2065,7 +2065,7 @@
"supportLevel" : "Stable",
"title" : "SSH Sink",
"summary" : "Runs the text of each message as a command on a remote server
over SSH, and returns what the command prints.",
- "description" : "Runs the text of each message as a command on a remote
server over SSH, and returns what the command prints.\n\nUse it to run a script
or a maintenance command on a server when something happens, for example
restart a service after a deployment or clear a cache when data changes. To run
a fixed command on a schedule and read its output, use `ssh-source`; to run a
command on the machine of the integration, use `exec-sink`.\n\nInput: the body
is the command to run, as [...]
+ "description" : "Runs the text of each message as a command on a remote
server over SSH, and returns what the command prints.\n\nUse it to run a script
or a maintenance command on a server when something happens, for example
restart a service after a deployment or clear a cache when data changes. To run
a fixed command on a schedule and read its output, use `ssh-source`; to run a
command on the machine of the integration, use `exec-sink`.\n\nInput: the body
is the command to run, as [...]
"group" : "SSH",
"namespace" : "File",
"provider" : "Apache Software Foundation"
diff --git
a/library/camel-kamelets/src/main/resources/kamelets/dns-dig-action.kamelet.yaml
b/library/camel-kamelets/src/main/resources/kamelets/dns-dig-action.kamelet.yaml
index 16b0c7557..cece64287 100644
---
a/library/camel-kamelets/src/main/resources/kamelets/dns-dig-action.kamelet.yaml
+++
b/library/camel-kamelets/src/main/resources/kamelets/dns-dig-action.kamelet.yaml
@@ -37,7 +37,7 @@ spec:
Input: the name to look up, taken from the `domain-name` header, else
from the `ce-domainname` header, else from the body as text. The kind of record
comes from the `dns-type` header, else from the `ce-dnstype` header, else it is
`A` (the IPv4 addresses).
- Output: the body is the whole answer as text, as the `dig` command shows
it: the question, the records found, and the status, such as `NOERROR`.
+ Output: the body is the whole answer as text, as the `dig` command shows
it: the question, the records found, and the status, such as `NOERROR`. The
`Content-Type` header is set to `text/plain`.
Good to know: a name the DNS does not know does not fail the message:
the answer has the status `NXDOMAIN` and no records. The Kamelet has no
options; it asks the DNS servers of the machine it runs on. Headers that start
with `CamelDns` are removed from the message first, so they cannot change what
the Kamelet does.
type: object
@@ -60,6 +60,13 @@ spec:
title: Record Type (CloudEvents)
description: "The kind of record to ask for, when the message is a
CloudEvent. Used only when `dns-type` is not set."
type: string
+ out:
+ default: text
+ types:
+ text:
+ format: "text-plain"
+ description: "The answer, as the text that the dig command shows."
+ mediaType: text/plain
dependencies:
- "camel:dns"
- "camel:kamelet"
diff --git
a/library/camel-kamelets/src/main/resources/kamelets/dns-ip-action.kamelet.yaml
b/library/camel-kamelets/src/main/resources/kamelets/dns-ip-action.kamelet.yaml
index a80dd0187..ee59dc05e 100644
---
a/library/camel-kamelets/src/main/resources/kamelets/dns-ip-action.kamelet.yaml
+++
b/library/camel-kamelets/src/main/resources/kamelets/dns-ip-action.kamelet.yaml
@@ -38,7 +38,7 @@ spec:
Input: the name to look up, taken from the `domain` header, else from
the `ce-domain` header, else from the body as text.
- Output: the body is one IP address, as text, such as `151.101.2.132`.
+ Output: the body is one IP address, as text, such as `151.101.2.132`,
and the `Content-Type` header is set to `text/plain`.
Good to know: when a name has several addresses, only one of them is
given. A name the DNS does not know fails the message with an unknown host
error. The headers are `domain` and `ce-domain`, not `domain-name` as for
`dns-lookup-action` and `dns-dig-action`. The Kamelet has no options; it uses
the name resolution of the machine it runs on. Headers that start with
`CamelDns` are removed from the message first, so they cannot change what the
Kamelet does.
type: object
@@ -53,6 +53,13 @@ spec:
title: Domain (CloudEvents)
description: "The host name to look up, when the message is a
CloudEvent. Used only when `domain` is not set."
type: string
+ out:
+ default: text
+ types:
+ text:
+ format: "text-plain"
+ description: "The IP address, as text."
+ mediaType: text/plain
dependencies:
- "camel:dns"
- "camel:kamelet"
diff --git
a/library/camel-kamelets/src/main/resources/kamelets/dns-lookup-action.kamelet.yaml
b/library/camel-kamelets/src/main/resources/kamelets/dns-lookup-action.kamelet.yaml
index 51aad73df..7f3f564e3 100644
---
a/library/camel-kamelets/src/main/resources/kamelets/dns-lookup-action.kamelet.yaml
+++
b/library/camel-kamelets/src/main/resources/kamelets/dns-lookup-action.kamelet.yaml
@@ -37,7 +37,7 @@ spec:
Input: the name to look up, taken from the `domain-name` header, else
from the `ce-domainname` header, else from the body as text.
- Output: the body is a JSON array with one entry per record found. Each
entry has the type, the class and the time to live of the record.
+ Output: the body is a JSON array, as bytes, with one entry per record
found, and the `Content-Type` header is set to `application/json`. Each entry
has the type, the class and the time to live of the record.
Good to know: a name the DNS does not know fails the message with "host
not found". The Kamelet has no options; it asks the DNS servers of the machine
it runs on. Headers that start with `CamelDns` are removed from the message
first, so they cannot change what the Kamelet does.
type: object
@@ -55,6 +55,13 @@ spec:
title: Domain Name (CloudEvents)
description: The host name to look up, when the message is a
CloudEvent. Used only when `domain-name` is not set.
type: string
+ out:
+ default: json
+ types:
+ json:
+ format: "application-json"
+ description: "The records found, as a JSON array in bytes."
+ mediaType: application/json
dependencies:
- "camel:jackson3"
- "camel:dns"
diff --git
a/library/camel-kamelets/src/main/resources/kamelets/nominatim-geocode-action.kamelet.yaml
b/library/camel-kamelets/src/main/resources/kamelets/nominatim-geocode-action.kamelet.yaml
index 2dbca5824..d1536ef86 100644
---
a/library/camel-kamelets/src/main/resources/kamelets/nominatim-geocode-action.kamelet.yaml
+++
b/library/camel-kamelets/src/main/resources/kamelets/nominatim-geocode-action.kamelet.yaml
@@ -37,7 +37,7 @@ spec:
Input: the place name or address to look up, as text.
- Output: the body is JSON text: an array with the best match, with its
coordinates, its full address and its kind of place, or an empty array when
nothing matches. The headers give the same answer in short: `CamelGeoCoderLat`
and `CamelGeoCoderLng` (the coordinates), `CamelGeoCoderAddress` (the full
address found), `CamelGeoCoderCity`, `CamelGeoCoderCountryLong`,
`CamelGeoCoderPostalCode` and `CamelGeoCoderStatus`, which is `OK` when a place
was found and `ZERO_RESULTS` when none was.
+ Output: the body is JSON text, as bytes, with `Content-Type:
application/json`: an array with the best match, with its coordinates, its full
address and its kind of place, or an empty array when nothing matches. The
headers give the same answer in short: `CamelGeoCoderLat` and
`CamelGeoCoderLng` (the coordinates), `CamelGeoCoderAddress` (the full address
found), `CamelGeoCoderCity`, `CamelGeoCoderCountryLong`,
`CamelGeoCoderPostalCode` and `CamelGeoCoderStatus`, which is `OK` when [...]
Good to know: a place that is not found does not fail the message; check
`CamelGeoCoderStatus`. The public server `https://nominatim.openstreetmap.org`
limits how often it may be called; for many lookups, run your own Nominatim
server. Headers that start with `CamelGeoCoder` are removed from the message
first, so they cannot change what the Kamelet does.
required:
@@ -51,6 +51,7 @@ spec:
type: string
dataTypes:
out:
+ default: json
headers:
CamelGeoCoderStatus:
title: Status
@@ -88,6 +89,11 @@ spec:
title: Postal Code
description: The postal code of the place found.
type: string
+ types:
+ json:
+ format: "application-json"
+ description: "The best match, as a JSON array in bytes."
+ mediaType: application/json
types:
in:
mediaType: text/plain
diff --git
a/library/camel-kamelets/src/main/resources/kamelets/ssh-sink.kamelet.yaml
b/library/camel-kamelets/src/main/resources/kamelets/ssh-sink.kamelet.yaml
index caff37f1e..49ca36a5a 100644
--- a/library/camel-kamelets/src/main/resources/kamelets/ssh-sink.kamelet.yaml
+++ b/library/camel-kamelets/src/main/resources/kamelets/ssh-sink.kamelet.yaml
@@ -37,7 +37,7 @@ spec:
Input: the body is the command to run, as text, such as `systemctl
restart myapp`. It runs in the shell of `username`, so it can hold several
commands separated by `;`.
- Output: the body afterwards is what the command printed on its standard
output, as a stream. The `CamelSshExitValue` header holds the exit code of the
command, and `CamelSshStderr` what it printed on its standard error, as a
stream.
+ Output: the body afterwards is what the command printed on its standard
output, as a stream, and the `Content-Type` header is `text/plain`. The
`CamelSshExitValue` header holds the exit code of the command, and
`CamelSshStderr` what it printed on its standard error, as a stream.
Good to know: it runs whatever command it receives, with the rights of
`username`. Never send it messages from an untrusted source, and log in with an
account that may do only what is needed. A command that ends with an exit code
other than 0 does not fail the message: check `CamelSshExitValue`. Log in with
`password`, or with a private key in `privateKeyResource` when the server does
not take passwords; when a key is set, the password is not used. The key of the
server is checked [...]
required:
@@ -103,6 +103,13 @@ spec:
out:
mediaType: text/plain
dataTypes:
+ in:
+ default: text
+ types:
+ text:
+ format: "text-plain"
+ description: "The command to run, as text."
+ mediaType: text/plain
out:
headers:
CamelSshExitValue:
diff --git
a/tests/camel-kamelets-itest/src/test/resources/dns/dns-dig-action-route.citrus.it.yaml
b/tests/camel-kamelets-itest/src/test/resources/dns/dns-dig-action-route.citrus.it.yaml
index aafc699a3..a0fc45310 100644
---
a/tests/camel-kamelets-itest/src/test/resources/dns/dns-dig-action-route.citrus.it.yaml
+++
b/tests/camel-kamelets-itest/src/test/resources/dns/dns-dig-action-route.citrus.it.yaml
@@ -40,7 +40,7 @@ actions:
- name: "X-Body-Type"
value: 'java.lang.String'
- name: "X-Content-Type"
- value: 'ct='
+ value: 'ct=text/plain'
body:
data: '@contains(''opcode: QUERY'')@'
diff --git
a/tests/camel-kamelets-itest/src/test/resources/geo/nominatim-geocode-action-route.citrus.it.yaml
b/tests/camel-kamelets-itest/src/test/resources/geo/nominatim-geocode-action-route.citrus.it.yaml
index f206dec17..b735797ed 100644
---
a/tests/camel-kamelets-itest/src/test/resources/geo/nominatim-geocode-action-route.citrus.it.yaml
+++
b/tests/camel-kamelets-itest/src/test/resources/geo/nominatim-geocode-action-route.citrus.it.yaml
@@ -56,7 +56,7 @@ actions:
path: "/result"
headers:
- name: "X-Body-Type"
- value: 'org.apache.camel.converter.stream.InputStreamCache'
+ value: '[B'
- name: "X-Content-Type"
value: 'ct=application/json'
- name: "X-Lat"
diff --git
a/tests/camel-kamelets-itest/src/test/resources/ssh/ssh-sink-route.citrus.it.yaml
b/tests/camel-kamelets-itest/src/test/resources/ssh/ssh-sink-route.citrus.it.yaml
index 8bcb752c6..9ddf1c39a 100644
---
a/tests/camel-kamelets-itest/src/test/resources/ssh/ssh-sink-route.citrus.it.yaml
+++
b/tests/camel-kamelets-itest/src/test/resources/ssh/ssh-sink-route.citrus.it.yaml
@@ -75,7 +75,7 @@ actions:
- name: "X-Body-Type"
value:
'org.apache.camel.converter.stream.ByteArrayInputStreamCache'
- name: "X-Content-Type"
- value: 'ct='
+ value: 'ct=text/plain'
- name: "X-Ssh-Exit-Value"
value: '3'
- name: "X-Ssh-Stderr-Type"