davsclaus opened a new issue, #3240:
URL: https://github.com/apache/camel-kamelets/issues/3240

   Most sink and action Kamelets call a Camel component, and that component 
also reads its own `Camel...` headers from the message, such as 
`CamelAwsS3OverrideBucketName`, `CamelJmsDestinationName`, 
`CamelKafkaOverrideTimestamp`, `CamelSmppCommand` or `CamelHttpUri`. When such 
a header comes along with the message, for example from a source of another 
system earlier in the flow, it can change the bucket, the destination, the 
operation or the address that the Kamelet was configured with. `http-sink` 
already removes its HTTP headers before the call; the other Kamelets do not.
   
   Change: each sink and action that calls a component removes the headers of 
that component as its first step (`removeHeaders` with the prefix of the 
component, such as `CamelAwsS3*`). The steps of the template that set those 
headers on purpose, from options or from the `file`, `key` and similar headers, 
run after it, so they keep working. Headers that a Kamelet documents as input 
stay, for example `CamelSmppDestAddr` (smpp-sink), `CamelAwsS3ContentType` 
(aws-s3-sink), `CamelPulsarProducerMessageKey` (pulsar-sink), and 
`CamelKafkaKey` and `CamelKafkaOverrideTopic` (kafka-sink, which the key and 
router actions set).
   
   - About 90 Kamelets: the AWS, Azure, Google, IBM, messaging (JMS, Kafka, 
MQTT, NATS, Pulsar, RabbitMQ), storage, search, Jira, Telegram, SMPP and 
template Kamelets.
   - `rest-openapi-sink`, `ogcapi-features-action` and `azure-functions-sink` 
remove the `CamelHttp*` and `CamelRestHttp*` headers, as `http-sink` does.
   - `azure-functions-sink` sends the key in the `x-functions-key` header 
instead of the `code` query parameter, so the key is not part of the address of 
the request.
   - Each changed Kamelet says so in its "Good to know".
   - Not changed: `exec-sink` and `ssh-sink`, which take the command from 
headers by design, and the actions whose job is to set headers (the Kafka 
router and key actions, `insert-header-action`, ...).
   
   A flow that set such a header on purpose before a sink now has to use the 
option of the Kamelet instead, or call the Camel component directly. This goes 
in the upgrade notes (#3190).
   
   _Claude Code on behalf of Claus Ibsen_
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to