davsclaus opened a new pull request, #27301: URL: https://github.com/apache/camel/pull/27301
## Summary Restructures the Camel CLI documentation so it is easier to find and read, and fills gaps found by comparing the docs with the commands in the code. **Structure** - All Camel CLI pages are now in the nav, grouped (before, 13 pages were only reachable from the table on the landing page). - **Kubernetes plugin** page rewritten around deploying an application: `camel kubernetes run` in one step, or `camel kubernetes export` to a Maven project deployed with `./mvnw package k8s:deploy`. Image, configuration, probes, exposing HTTP, CPU/memory, OpenShift, troubleshooting. The trait options inherited from Camel K, CronJob, Knative, Jolokia, mounts and OpenAPI moved to a new **Kubernetes Plugin Advanced Options** page. The old build instructions (`quarkus.kubernetes.deploy`) were stale: all runtimes build and deploy with JKube. - New **AI Providers and Local Models** page: the provider detection order, Ollama and OpenAI-compatible servers were copied in three pages (and had drifted); now one page shared by the CLI and TUI pages. Adds IBM watsonx (supported, never documented) and notes that `camel harden` only detects Ollama. - New **Validation** page (from the devtools page), adding `camel validate properties` and `camel validate normalize`. - New **Diagnostics** page: `get error`, `get activity`, `get inflight`, `get blocked`, `cmd memory-leak`, heap histogram/dump, gc, thread dump, `get startup-recorder`, route structure/dump, `get datasource`, `get sql-trace`, `cmd sql`, `get kafka`, `get vault`. - Maven settings and running a Maven project moved from Tips to Running; container image content merged into one page. **Content** - Documented `camel dev`, `camel dirty`, `camel transform dataweave`, `camel generate rest`, and the ASF plugins. - Camel CLI branding; install via the installer script (Camel CLI Launcher) or JBang. - TUI tabs list includes the Secrets tab. **Command reference generation** - Plugin commands (kubernetes, test, tui, mcp, validate, generate, edit, route-parser) now get generated reference pages, listed in a *Plugin commands* section of the index. Each plugin module generates `META-INF/camel-jbang-plugin-commands-metadata.json`. - Generated pages whose command no longer exists are removed (the orphan `cmd jfr-old-objects` page); `validate yaml`/`normalize` pages are generated again, their examples kept in partials. **Small fixes** - Startup recorder hints said `camel.main.startup-recorder=true`, which is not a valid value; now `backlog`. The help example used `camel cmd startup-recorder`; it is `camel get startup-recorder`. ## Notes - `camel kubernetes --connect` fills a `serviceBinding` trait that no trait implementation reads, so it is not documented; to be followed up separately. - `camel test` reference lists only `init`; its other subcommands come from the Citrus library and cannot be parsed from source. ## Test plan - `UserManualDocExamplesTest` (camel-yaml-dsl-validator), `DocExamplesJavaImportsTest` and `DocExamplesXmlSchemaTest` (camel-catalog) pass, run without the build cache. - Checked every `xref:` to the Camel CLI pages (anchors included) across docs, components, core and dsl. - Core and the 8 plugin modules build; core command metadata regenerates unchanged. _Claude Code on behalf of davsclaus_ 🤖 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]
