Module sync 

Sync protocol types for agent ↔ manager communication.

The agent periodically calls POST /v1/sync with a SyncRequest and receives a SyncResponse containing the target deployment state.

Structs

OperationsBundleDownload

One bundle the Operator needs to download to reach targetBundleHash. The manager mints a short-lived presigned GET URL per bundle — the Operator never holds real cloud storage credentials, mirroring the OCI registry proxy’s credential-injection pattern.

OperationsReport

Report-only summary of the operations the Operator has loaded, used to confirm a bundle sync actually took effect.

OperatorCapabilityReport

Report-only Operator capability status.

OperatorImageReport

Exact immutable Operator image identity observed by the running process.

ReportedOperation

A single operation the Operator currently has loaded. Opaque identifiers only — no tier, description, or other plugin business logic crosses into this public crate.

SyncExecutionClaim

SyncInput

Extensible wire input for sync metadata that is not part of the long-standing SyncRequest struct-literal contract.

SyncInputBuilder

Builder for optional sync receipts. New optional wire metadata belongs here so adding it does not break downstream SyncRequest literals.

SyncRequest

Request sent by the agent to the manager during periodic sync.

SyncResponse

Response from the manager to the agent sync request.

TargetDeployment

Target deployment state for the agent to converge toward.

TargetOperationsBundleSet

Target operations-bundle set for the Operator to converge its loaded plugin registry toward, independent of any release/config target — a plugin can be enabled with no release change, so this is not nested under TargetDeployment.

Enums

OperatorCapabilityState

State of an Operator capability as observed inside the environment.

OperatorImageSource

Origin of the exact Operator image running this process.