The CLI can import artifacts and run tests, but it cannot currently show which services are already loaded in a Microcks instance. That makes local debugging and CI troubleshooting harder than it needs to be, because the user has to open the web UI just to confirm what is available before running a test.
Microcks already exposes service repository APIs such as /api/services and /api/services/map, so this feels like a natural CLI capability.
A possible command could be:
microcks services
# or
microcks services list
The default output could be a simple table with fields such as:
- service name
- version
- type
- last update or import date, if the API response exposes it cleanly
A JSON output mode could also be useful for scripts, if that matches the direction maintainers want for CLI output.
A first PR could keep the scope focused:
- add service DTOs in
pkg/connectors
- add
MicrocksClient.GetServices
- add a Cobra command under
cmd/
- reuse the same auth and context resolution pattern as existing commands
- add
httptest coverage for the client method and command output
- update command documentation
This would also be useful groundwork for the LFX VS Code integration work in #255, since listing loaded services is one of the expected editor views.
@lbroudoux @yada @Harsh4902 would this fit the CLI roadmap? If yes, I can work on a focused PR for the first version.
The CLI can import artifacts and run tests, but it cannot currently show which services are already loaded in a Microcks instance. That makes local debugging and CI troubleshooting harder than it needs to be, because the user has to open the web UI just to confirm what is available before running a test.
Microcks already exposes service repository APIs such as
/api/servicesand/api/services/map, so this feels like a natural CLI capability.A possible command could be:
microcks services # or microcks services listThe default output could be a simple table with fields such as:
A JSON output mode could also be useful for scripts, if that matches the direction maintainers want for CLI output.
A first PR could keep the scope focused:
pkg/connectorsMicrocksClient.GetServicescmd/httptestcoverage for the client method and command outputThis would also be useful groundwork for the LFX VS Code integration work in #255, since listing loaded services is one of the expected editor views.
@lbroudoux @yada @Harsh4902 would this fit the CLI roadmap? If yes, I can work on a focused PR for the first version.