/*
* Hanzo Cloud API
*
* The Hanzo Cloud API as a customer calls it: every operation under /v1/ except the operator's admin product, relay routes, legacy spellings and capabilities still reached by flag. Tagged by product: the first path segment after /v1/.
*
* The version of the OpenAPI document: v1
*
* Generated by: https://openapi-generator.tech
*/
use crate::models;
use serde::{Deserialize, Serialize};
#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)]
pub struct RiskDisposeOut {
/// Before echoes the retention boundary that was applied, RFC 3339 in UTC, as this plane parsed it from the request. What was disposed of is every record WRITTEN strictly before it and not under litigation hold — written, measured against the server clock at the write, and not against the event or observation times the asserting caller supplies, because a tenant that could back-date could delete a compliance record on demand. A boundary younger than the platform floor of five years is refused before anything is removed.
#[serde(rename = "before", skip_serializing_if = "Option::is_none")]
pub before: Option<String>,
/// Disposed is how many whole records were removed. Records are disposed of whole, never redacted: a partially-erased compliance record is one nobody can attest to.
#[serde(rename = "disposed", skip_serializing_if = "Option::is_none")]
pub disposed: Option<i32>,
/// Held is how many records inside the boundary were kept under litigation hold.
#[serde(rename = "held", skip_serializing_if = "Option::is_none")]
pub held: Option<i32>,
/// Oldest is the WRITE time of the oldest assertion this tenant still holds after the sweep, RFC 3339, and it is omitted exactly when nothing remains at all. Still older than Before means records survived on purpose and says which mechanism kept them: a litigation hold (Held), or the per-call bound with more to sweep on the next call (Remaining).
#[serde(rename = "oldest", skip_serializing_if = "Option::is_none")]
pub oldest: Option<String>,
/// Remaining is how many disposable records are still older than the boundary. A sweep is bounded per call, so a non-zero value here means call again rather than that something failed.
#[serde(rename = "remaining", skip_serializing_if = "Option::is_none")]
pub remaining: Option<i32>,
/// Restored is how many records this sweep had already removed from the derived columnar copy and then did NOT dispose of, because a litigation hold arrived between the identify and the delete — and which were therefore written back to the derived copy before this answered. It is a NAMED state and not a silent repair. The copy is swept before the record so nothing is orphaned in the warehouse, which means a record the delete declines to remove is one the warehouse has already lost, with its seq behind the delivery cursor and no retry that can reach it. Non-zero here says the collision happened and was repaired; a non-zero that keeps recurring says retention and hold are racing on the same records, which is worth an operator's attention rather than a debug line.
#[serde(rename = "restored", skip_serializing_if = "Option::is_none")]
pub restored: Option<i32>,
/// Total and Oldest describe what the tenant still holds afterwards, so a disposal that removed nothing is distinguishable from a tenant that had nothing.
#[serde(rename = "total", skip_serializing_if = "Option::is_none")]
pub total: Option<i32>,
}
impl RiskDisposeOut {
pub fn new() -> RiskDisposeOut {
RiskDisposeOut {
before: None,
disposed: None,
held: None,
oldest: None,
remaining: None,
restored: None,
total: None,
}
}
}