gnodet opened a new pull request, #22169: URL: https://github.com/apache/camel/pull/22169
## Summary - Add `--json` option to `ProcessWatchCommand` base class so all subclasses (process watch commands) inherit it - Add JSON output support to 26 camel-jbang commands that produce tabular output using AsciiTable - Commands now support `--json` flag to output structured JSON instead of ASCII table format - `ListTransformer` (extends `ProcessBaseCommand`) gets its own `--json` option since it doesn't extend `ProcessWatchCommand` ### Commands with new `--json` support: - `get context` (CamelContextStatus) - `top context` (CamelContextTop) - `get route` / `top route` (CamelRouteStatus / CamelRouteTop) - `get route-group` / `top group` (CamelRouteGroupStatus / CamelRouteGroupTop) - `get processor` (CamelProcessorStatus) - `count` (CamelCount) - `get endpoint` (ListEndpoint) - `get health` (ListHealth) - `get service` (ListService) - `get variable` (ListVariable) - `get consumer` (ListConsumer) - `get producer` (ListProducer) - `get inflight` (ListInflight) - `get blocked` (ListBlocked) - `get event` (ListEvent) - `get rest` (ListRest) - `get platform-http` (ListPlatformHttp) - `get circuit-breaker` (ListCircuitBreaker) - `get properties` (ListProperties) - `get vault` (ListVault) - `get metric` (ListMetric) - `get kafka` (ListKafka) - `get groovy` (ListGroovy) - `get transformer` (ListTransformer) - `get internal-tasks` (ListInternalTask) ### Already had `--json` support (unchanged): - `ps` (ListProcess) - removed duplicate `jsonOutput` field since it now inherits from `ProcessWatchCommand` ## Test plan - [x] Build passes (`mvn install -DskipTests`) - [x] Code formatting verified (`mvn formatter:format impsort:sort`) - [x] Unit tests pass (245/246, 1 pre-existing failure unrelated to this change) -- 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]
