ant-service-management

Crates.ioant-service-management
lib.rsant-service-management
version0.4.16
created_at2024-12-18 14:11:28.740905+00
updated_at2025-09-03 17:13:35.836738+00
descriptionA command-line application for installing, managing and operating `antnode` as a service.
homepagehttps://maidsafe.net
repositoryhttps://github.com/maidsafe/autonomi
max_upload_size
id1487721
size258,109
MaidSafe-QA (MaidSafe-QA)

documentation

README

Service Management

Provides utilities for dealing with services, which are mainly used by the node manager.

RPC Actions

The RpcActions trait defines the protocol that is currently available for interacting with antnode:

node_info: Returns information about the node, such as its peer ID and version.
network_info: Retrieves network-related information, such as the peers currently connected to the node.
record_addresses: Provides a list of the node's record addresses.
restart_node: Requests the node to restart.
stop_node: Requests the node to stop its operations.
update_node: Updates the node with provided parameters.

Users of the crate can program against the trait rather than the RpcClient implementation.

This can facilitate behaviour-based unit testing, like so:

use mockall::mock;
use mockall::predicate::*;

mock! {
    pub RpcClient {}
    #[async_trait]
    impl RpcClientInterface for RpcClient {
        async fn node_info(&self) -> RpcResult<NodeInfo>;
        async fn network_info(&self) -> RpcResult<NetworkInfo>;
        async fn record_addresses(&self) -> Result<Vec<RecordAddress>>;
        async fn gossipsub_subscribe(&self, topic: &str) -> Result<()>;
        async fn gossipsub_unsubscribe(&self, topic: &str) -> Result<()>;
        async fn gossipsub_publish(&self, topic: &str, message: &str) -> Result<()>;
        async fn node_restart(&self, delay_millis: u64) -> Result<()>;
        async fn node_stop(&self, delay_millis: u64) -> Result<()>;
        async fn node_update(&self, delay_millis: u64) -> Result<()>;
    }
}
Commit count: 7360

cargo fmt