davsclaus opened a new pull request, #3251:
URL: https://github.com/apache/camel-kamelets/pull/3251

   Fixes #3163.
   
   The `cloudevents` output data type of two Kamelets described the 
`CamelCloudEventSource` header as a receipt handle. Neither is.
   
   | Kamelet | Before | Now |
   |---|---|---|
   | `aws-sqs-source` | the SQS receipt handle with the prefix `aws.sqs.queue.` 
| the name of the SQS queue with the prefix `aws.sqs.queue.`, such as 
`aws.sqs.queue.orders` |
   | `aws-ddb-streams-source` | the DDB Stream event source receipt handle with 
the prefix `aws.ddbstream.` | the event source of the stream record with the 
prefix `aws.ddbstream.`, which is `aws.ddbstream.aws:dynamodb` |
   
   From Camel 4.24 the `aws2-sqs:application-cloudevents` transformer takes the 
queue name from the `CamelAwsSqsQueueName` header (CAMEL-26300). The catalog 
builds against 4.24 since #3202, so the SQS half could be fixed now as well.
   
   ### Checked by running
   With `camel run` (Camel 4.24.0-SNAPSHOT) against Floci: each Kamelet, 
followed by `data-type-action` with `application-cloudevents`, logged:
   
   ```
   SQS source=aws.sqs.queue.orders-q
   DDB source=aws.ddbstream.aws:dynamodb eventSource=aws:dynamodb
   ```
   
   Only the two descriptions change. `./mvnw clean install` regenerated the 
library copy and passes.
   
   _Claude Code on behalf of Claus Ibsen_
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
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