davsclaus opened a new pull request, #29747:
URL: https://github.com/apache/camel/pull/29747

   ## Summary
   
   [CAMEL-22280](https://issues.apache.org/jira/browse/CAMEL-22280): `camel 
infra ps` shows which Docker container a running service is in, so you can use 
it with `docker exec`, `docker logs` or `docker inspect`.
   
   - `camel infra run` keeps the container name and short id with the service 
data (`containerName`, `containerId`). They are printed at startup, shown by 
`camel infra get`, included in `camel infra ps --json` and shown in the TUI's 
infra details. A service that runs embedded has neither.
   - `camel infra ps` has a CONTAINER column. It shows the name, or the short 
id when there is no name. `camel infra list` doesn't have the column.
   - Fixed in the same table: IMPLEMENTATION cut off the end of its text even 
when it had room (`confluent, redpanda, stri…`). The max width of an asciitable 
column includes its padding, and the measured width doesn't.
   
   ```
     PID    ALIAS              IMPLEMENTATION  UI  DESCRIPTION                  
                             CONTAINER        SERVICE_DATA
    320293  mosquitto                              Mosquitto is a message 
broker that implements MQTT prot…  camel-mosquitto  {"brokerUrl":"tcp://localho…
   ```
   
   ## Test plan
   
   - [x] New `InfraRunContainerTest` (container name and short id, and a 
service without a container) and 
`InfraPsTest.shouldShowTheContainerOfARunningService`.
   - [x] All `Infra*Test` in camel-jbang-core pass (51 tests).
   - [x] Live: `camel infra run mosquitto` from the worktree's launcher. `camel 
infra ps` shows `camel-mosquitto`, and `--json` shows `containerId` 
`618161f2498a`, the same as `docker ps`.
   
   _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]

Reply via email to