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

   Part of #3162, group 1: this removes the 11 Kamelets that cannot work on 
Camel 4.23 or 4.24. Andrea agreed to the plan on the issue.
   
   | Kamelet | Why it cannot work |
   |---|---|
   | `twitter-directmessage-source`, `twitter-search-source`, 
`twitter-timeline-source` | The Twitter/X API v1.1 endpoints they call are gone 
or paid-only. Every tweet fails (`marshal: json` cannot write `LocalDateTime`). 
|
   | `chunk-template-action` | It has never loaded its template: `base64:` is 
not a resource scheme, so the body becomes `[chtml template '...' not found]`. 
Use `mustache-template-action`, `velocity-template-action`, 
`freemarker-template-action` or `string-template-action` instead. |
   | `djl-image-to-text-action` | Fails on every image with a 
`RasterFormatException`. |
   | `aws-sts-assume-role-action` | Does not start: `Unknown parameters 
useSessionCredentials`, an option that aws2-sts does not have. |
   | `kafka-azure-schema-registry-sink`, `kafka-azure-schema-registry-source`, 
`kafka-batch-azure-schema-registry-source` | Do not start 
(`NoSuchBeanException`): `#bean:defaultAzureCredential` is a literal, but the 
template's bean names are made unique. |
   | `dropbox-source`, `dropbox-sink` | Do not start ("option `expireIn` is not 
present"): the component now needs refresh-token options that the Kamelets do 
not have. |
   
   The Kamelets are removed in one step, with no deprecation release first. 
That is how #3093 and #2831 removed Kamelets, and a Kamelet that does not start 
gains nothing from a deprecation period.
   
   ### Removed with them
   
   - The Kamelet YAML and its copy in `library/camel-kamelets`
   - 9 doc partials and 12 pipe templates
   - The `KameletsCatalogTest` header lines; the AWS namespace count drops from 
32 to 31
   - The `dropbox` and `twitter-*` entries of `KameletPrefixSchemeEnum`, as 
#2831 did for the AMQP SSL Kamelets
   - The validator exemptions for the three Azure Schema Registry Kamelets, in 
`CatalogValidator` and `ValidateKameletsMojo`. One of these names had a typo 
(`registy`), so that exemption never matched anything.
   - The mentions in `security-model.adoc` and in the 
`kafka-apicurio-registry-not-secured-sink` description
   
   `nav.adoc`, `kamelets-index.json` and the catalog SBOM are regenerated.
   
   The developer guide still uses a `twitter-search-source` as its "write your 
first Kamelet" walk-through. It shows how to write the Kamelet, not how to use 
the catalog one, so it is left as it is.
   
   ### Verification
   
   `./mvnw clean install` passed twice, the first time with `-DskipTests`.
   
   _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