lburgazzoli commented on PR #13408:
URL: https://github.com/apache/camel/pull/13408#issuecomment-1983349599
This PR is mainly aimed as exploring a possible came-k sub command to
inspect routes and provide insight to the camel-k operator. The goal is to use
this as a sidecar so the sub-command starts a simple http server (based on
vertx).
The result of the inspection is something like:
```json
{
"capabilities": [
"platform-http",
"circuit-breaker"
],
"dependencies": [
"mvn:org.apache.camel/camel-core-languages/4.5.0-SNAPSHOT",
"mvn:org.apache.camel/camel-jackson/4.5.0-SNAPSHOT",
"mvn:org.apache.camel/camel-kafka/4.5.0-SNAPSHOT",
"mvn:org.apache.camel/camel-knative/4.5.0-SNAPSHOT",
"mvn:org.apache.camel/camel-log/4.5.0-SNAPSHOT",
"mvn:org.apache.camel/camel-platform-http/4.5.0-SNAPSHOT"
],
"endpoints": {
"from": [
"platform-http:///foo";
],
"to": [
"kafka://topic",
"knative://event/foo?apiVersion=eventing.knavine.dev/v1alpha1&kind=Channel&name=bar",
"log://info"
]
},
"resourcs": {
"components": [
"kafka",
"knative",
"log",
"platform-http"
],
"dataformats": [
"jackson"
],
"languages": [
"constant",
"simple"
]
}
}
```
NOTES:
1. there are code duplication and custom logic inspired by other camel-jbang
subcommand that may be refactored at some point, but I didn't want to go that
far as this stage
2. the code is still a work in progress and not all the possible cases have
been taken into account
3. some enhancement on the camel-catalog, like having the option to add some
metadata would be very welcome
4. there is the potential to get rid of the camel-k specific catalog and
rely on the camel's one in the future
@davsclaus I would really appreciate your feedback
--
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: commits-unsubscr...@camel.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
