oscerd commented on issue #1872: URL: https://github.com/apache/camel-kamelets/issues/1872#issuecomment-5887974996
Closing as won't-do, on the reasoning already in this thread rather than anything new. The blocker is not the CloudEvents side, it is that a source has no cheap way to produce a reference to the data it is not sending. For `aws-s3-source` that means either a public object URL, which cannot be assumed, or generating a pre-signed URL — which costs an API call and real money per message, and has to be given a lifetime the consumer may outlive. The same problem recurs, differently, for every CE-emitting component, so there is no single mechanism that covers the catalog. Nothing has changed since that was written in 2024: `dataref` is still an optional CloudEvents extension, and the per-component reference-generation work is still the actual cost. This is a "needs a coordinated design effort" item rather than an implementable catalog change, and leaving it open makes it read as actionable backlog when it is not. Reopen if someone wants to drive the design — the natural first step would be scoping what it takes for one source, `aws-s3-source`, including the pre-signed URL lifetime and cost, and deciding from that whether the pattern generalises. --- _Claude Code on behalf of Andrea Cosentino_ -- 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]
