Module scheduler 

Modules

debug_client

Generated client implementations.

debug_server

Generated server implementations.

pairing_client

Generated client implementations.

pairing_server

Generated server implementations.

scheduler_client

Generated client implementations.

scheduler_server

Generated server implementations.

signer_request

Nested message and enum types in SignerRequest.

signer_response

Nested message and enum types in SignerResponse.

Structs

AddOutgoingWebhookRequest

AddOutgoingWebhookResponse

ApprovePairingRequest

ApprovePairingResponse

ChallengeRequest

ChallengeResponse

DeleteOutgoingWebhooksRequest

ExportNodeRequest

Empty message for now, node identity is extracted from the mTLS certificate used to authenticate against the Scheduler.

ExportNodeResponse

GetPairingDataRequest

GetPairingDataResponse

InviteCode

ListInviteCodesRequest

ListInviteCodesResponse

ListOutgoingWebhooksRequest

ListOutgoingWebhooksResponse

NodeInfoRequest

Discovery request asking the scheduler if a nodelet is currently assigned the specified node_id, or wait for one to be assigned. If wait is set to true the scheduler will keep the request pending until a nodelet is assigned.

NodeInfoResponse

PairDeviceRequest

PairDeviceResponse

RecoveryRequest

RecoveryResponse

RegistrationRequest

RegistrationResponse

RotateOutgoingWebhookSecretRequest

ScheduleRequest

Ask the scheduler to schedule the node to be run on an available nodelet.

SignerRejection

SignerRequest

SignerResponse

StartupMessage

A message that we know will be requested by lightningd at startup, and that we stash a response to on the scheduler. This allows the scheduler to start a node without requiring the signer to connect first. Messages are stored in full, including type prefix, but without the length prefix.

UpgradeRequest

UpgradeResponse

Webhook

WebhookSecretResponse

Enums

ChallengeScope

Operation is the challenge associated with?