Claus Ibsen created CAMEL-25433:
-----------------------------------
Summary: camel-jbang - camel run --example and the monitor show
what an example needs before it runs
Key: CAMEL-25433
URL: https://issues.apache.org/jira/browse/CAMEL-25433
Project: Camel
Issue Type: Improvement
Components: camel-jbang
Reporter: Claus Ibsen
Fix For: 4.23.0
Some examples need something before they run: a model pulled into Ollama
(ai/langchain4j-chat: ollama pull granite4:3b), an API key
(ai/openai-pii-redaction: OPENAI_API_KEY), or another example running first
(contracts/openapi-client needs contracts/openapi-server). Without it they fail
on every message or at startup, and nothing says why before the run.
The example catalog carries what an example needs (the needs field of its
metadata.json, now concrete in camel-jbang-examples), but the tools do not show
it.
Proposal: show it before the run, so the user can do it by hand:
* camel run --example prints "Needs: ..." before it starts the example, and the
group listing shows it
* the camel-jbang monitor shows it in the example browser and in the notice
when an example is started; its MCP tool that runs an example returns it
* the bundled example catalog is synced from camel-jbang-examples (the new
needs texts; showcase/smart-log-analyzer leaves the catalog)
See apache/camel-jbang-examples#99.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
