pub struct SyncResponse {
pub execution_claim: Option<SyncExecutionClaim>,
pub current_state: Option<DeploymentState>,
pub target: Option<TargetDeployment>,
pub commands_url: Option<String>,
pub target_operations_bundle_set: Option<TargetOperationsBundleSet>,
}Expand description
Response from the manager to the agent sync request.
Fields§
§execution_claim: Option<SyncExecutionClaim>Exact operation attempt associated with target.
current_state: Option<DeploymentState>Authoritative deployment state from the manager.
Pull agents use this to hydrate local state when attaching to an already-imported deployment. Absent means the agent’s local state is already authoritative or no state has been established yet.
target: Option<TargetDeployment>Target deployment the agent should converge toward. None means no changes needed or this is an observe-only deployment.
commands_url: Option<String>Public URL for the commands API (e.g. https://manager.example.com/v1).
Operators and app-owned receivers use this to lease pending commands;
Workers themselves receive pushes.
When absent, the agent falls back to its sync URL.
target_operations_bundle_set: Option<TargetOperationsBundleSet>Target operations-bundle set the Operator should converge its loaded
plugin registry toward. None means no enabled plugin set has ever
been established for this project (nothing to sync), not that the
Operator is up to date — compare hash against the Operator’s own
loaded hash to decide whether to download anything.