Refactore and improve activemq CLI
- Dominant language
- Java
- Stars
- 2.5k
- Forks
- 1.5k
- Avg merge
- 10h 46m
- Merged PRs (30d)
- 79
Description
If we already have a CLI (`activemq`), I strongly believe we should improve the CLI with more "user facing" operations (similar to what we can find on the Web Console):
1. Listing all resources (destinations, transport connectors, network connectors, etc)
2. Managing resources (create/delete/update destinations, transport connectors, network connectors, etc)
3. Managing messages (browse/produce/consume)
4. Getting internal broker resources (scheduler, broker attributes, ...)
The purpose is not to "expose" the JMX MBeans (as we can do today with `activemq bstat`, `activemq dstat`, or `activemq query -Qqueue`, etc).
The purpose is to façade with user friendly CLI:
```
activemq queues create FOO
activemq queues delete FOO
activemq queues purge FOO
...
```
Why do I think it's important ?
Because we would be able to "integrate" easily ActiveMQ via the CLI into Claude Code and similar (no need to create a MCP server anymore if the CLI is good enough).
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.