openzeppelin_relayer::api::controllers::relayer

Function delete_relayer

Source 
pub async fn delete_relayer<J, RR, TR, NR, NFR, SR, TCR, PR>(
    relayer_id: String,
    state: ThinDataAppState<J, RR, TR, NR, NFR, SR, TCR, PR>,
) -> Result<HttpResponse, ApiError>
where
    J: JobProducerTrait + Send + Sync + 'static,
    RR: RelayerRepository + Repository<RelayerRepoModel, String> + Send + Sync + 'static,
    TR: TransactionRepository + Repository<TransactionRepoModel, String> + Send + Sync + 'static,
    NR: NetworkRepository + Repository<NetworkRepoModel, String> + Send + Sync + 'static,
    NFR: Repository<NotificationRepoModel, String> + Send + Sync + 'static,
    SR: Repository<SignerRepoModel, String> + Send + Sync + 'static,
    TCR: TransactionCounterTrait + Send + Sync + 'static,
    PR: PluginRepositoryTrait + Send + Sync + 'static,
Expand description

Deletes a relayer by ID.

§Arguments

  • relayer_id - The ID of the relayer to delete.
  • state - The application state containing the relayer repository.

§Returns

A success response or an error if deletion fails.

§Security

This endpoint ensures that relayers cannot be deleted if they have any pending or active transactions. This prevents data loss and maintains system integrity.