Command - there are typed interfaces to implement commands

[etorreborre]

Following the refactoring of RPC calls, we can now implement all commands using typed interfaces and implemented with a specific RPC client.

For example the Projects trait provides an access to projects, to create/list/delete them. That trait is implemented by the Controller client by making requests to the controller.

The use of the Projects interface can be seen in the following command to create projects.

The purpose of this epic is to provide similar interfaces for all other commands and remove all the "api helpers" from the ockam_command crate:

• inlets
• outlets
• secure channel
• secure channel listener
• services
• nodes
• workers
• tcp connections
• relays
• policies
• kafka services

All the interfaces and implementations must be part of the ockam_api crate so that the purpose of the ockam_command is only to:

• get and validate arguments from the command line
• call the ockam_api crate
• display progress / reports / outputs / errors

Note

Github project tracking these issues: https://github.com/orgs/build-trust/projects/37/views/1?filterQuery=eric+

Related issues:

• Command - refactor to use typed interfaces to implement commands for inlets and outlets #6698
• Command - refactor to use typed interfaces to implement commands for secure channel and secure channel listener #6699
• Command - refactor to use typed interfaces to implement commands for services #6700
• Command - refactor to use typed interfaces to implement commands for nodes #6701
• Command - refactor to use typed interfaces to implement commands for workers #6702
• Command - refactor to use typed interfaces to implement commands for tcp connections #6703
• Command - refactor to use typed interfaces to implement commands for relays #6704
• Command - refactor to use typed interfaces to implement commands for policies #6705
• Command - refactor to use typed interfaces to implement commands for kafka services #6706