Claus Ibsen created CAMEL-26716:
-----------------------------------

             Summary: camel-jbang - Good to know: hints about an integration 
from one shared rule set (About screen, security scan, Doctor)
                 Key: CAMEL-26716
                 URL: https://issues.apache.org/jira/browse/CAMEL-26716
             Project: Camel
          Issue Type: Improvement
          Components: camel-jbang
            Reporter: Claus Ibsen
             Fix For: 4.24.0


The About screen of the TUI (CAMEL-26700) should end with *Good to know*: a few 
lines, each answering one question a newcomer to an integration has, from the 
route model, saying what happens (a hint, not a fix):

* *When it fails*: per entry point, retried N times then the dead letter 
channel, returned to the HTTP caller as 500, or logged and gone.
* *What is dropped*: a filter, a choice without otherwise, the duplicates an 
idempotent consumer skips.
* *What does not wait*: a wire tap, a seda: hand-off, inOnly; a failure there 
is not seen by the caller.
* *What a restart forgets*: an idempotent or aggregation repository in memory.
* *Twice or out of order*: an input that redelivers (Kafka, JMS) before a call 
out without an idempotent consumer; parallel processing or concurrent consumers.
* *What is exposed or insecure*: a call to another host over a plain transport 
(http:, ftp:, smtp:, Kafka PLAINTEXT) where a secure one exists; an option the 
catalog marks insecure set to its insecure value (security = "insecure:ssl", 
"insecure:serialization", "insecure:dev", such as trustAllCertificates=true); 
an option marked secret written as plain text instead of a {{placeholder}} or a 
vault; an HTTP server without authentication on all interfaces. A plain 
transport to localhost is no hint.

The hints should not be a set picked while building the screen. They belong to 
one curated set of rules that more tools share, kept in camel-jbang-core:

* today's ProjectOverview findings,
* the camel_security_scan and harden tools of camel-jbang-mcp (their rules move 
from camel-jbang-mcp to camel-jbang-core, so the screen and the tools agree),
* the Doctor,
* the option metadata of the catalog (secret, security = "insecure:*").

Then the same hints are in the About screen, in camel get about (CAMEL-26700, 
stage 5) and for an AI over MCP.

To be talked over before it is built (decided on the walk of the About screen, 
7 Nov 2026). Design: https://claude.ai/artifact/2H927wodRp3FAy1BbDbw3P (section 
"For you to decide").

_Claude Code on behalf of Claus Ibsen_



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to