pub struct RollbackResponse {
pub log_entry_version_id: String,
pub effective_at: String,
pub kind: String,
pub drain_until: Option<String>,
pub draining_mediator: Option<String>,
pub vta_did: String,
pub serverless: bool,
}Expand description
Response body for the rollback handlers. Wider than
ServiceMutationResponse — adds kind and
draining_mediator fields that downstream consumers need to
distinguish the dispatched arm.
log_entry_version_id is the empty string when the rollback
was a no-op (snapshot ≡ current state).
Fields§
§log_entry_version_id: String§effective_at: String§kind: StringOne of: disabled, enabled, updated, no_op.
drain_until: Option<String>Some(rfc3339) when the rollback scheduled a drain.
None for REST and DIDComm enable / no-op arms.
draining_mediator: Option<String>Mediator DID currently being drained by this rollback.
None for REST and DIDComm enable / no-op arms.
vta_did: StringThe VTA’s own DID — the subject of the LogEntry this
rollback wrote. Carried so the CLI can print follow-up
commands like pnm webvh did-log <vta_did> for serverless
deployments without forcing the operator to look it up.
Empty string in no_op responses where no LogEntry was
written. Serialized as vta_did on the wire; elided when
empty for compactness.
serverless: boolTrue when the VTA’s DID is self-hosted (server_id = "serverless"). The rollback’s new LogEntry is persisted
locally but NOT pushed to any webvh host — the operator
must fetch the updated did.jsonl and redeploy.
#[serde(default)] for back-compat — older servers don’t
emit the field and old clients treat absent → false.
Trait Implementations§
Source§impl Clone for RollbackResponse
impl Clone for RollbackResponse
Source§fn clone(&self) -> RollbackResponse
fn clone(&self) -> RollbackResponse
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more