hanzo-client 8.5.156

Generated client for the Hanzo API — every service, one crate.
Documentation
/*
 * 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 RiskHoldIn {
    /// Hold is the state to put them in: true places the hold, false releases it. One op both ways, because a hold that can be placed and not released pins a compliance record past every retention boundary with nothing able to let it go — and an operator who cannot release a hold stops placing them.
    #[serde(rename = "hold", skip_serializing_if = "Option::is_none")]
    pub hold: Option<bool>,
    /// IDs are the content digests of the records, as returned by the write and by the read. They name records in THIS tenant's plane; an id belonging to anybody else names nothing here, because the statement runs against this tenant's own file and there is no other file it could reach.
    #[serde(rename = "ids", skip_serializing_if = "Option::is_none")]
    pub ids: Option<Vec<String>>,
}

impl RiskHoldIn {
    pub fn new() -> RiskHoldIn {
        RiskHoldIn {
            hold: None,
            ids: None,
        }
    }
}