Skip to main content

hanzo_client/models/
reference_override_in.rs

1/*
2 * Hanzo Cloud API
3 *
4 * 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/.
5 *
6 * The version of the OpenAPI document: v1
7 * 
8 * Generated by: https://openapi-generator.tech
9 */
10
11use crate::models;
12use serde::{Deserialize, Serialize};
13
14#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)]
15pub struct ReferenceOverrideIn {
16    /// Key is the member: a domain, a CIDR or address, an issuer prefix, a device digest. It is matched the same way the baseline is, so a deny on tempbox.example also covers mail.tempbox.example.
17    #[serde(rename = "key", skip_serializing_if = "Option::is_none")]
18    pub key: Option<String>,
19    /// Note is why, in your own words. Optional, bounded to 512 bytes.
20    #[serde(rename = "note", skip_serializing_if = "Option::is_none")]
21    pub note: Option<String>,
22    /// Verdict is allow or deny, and nothing else. An override is a decision — unlike a baseline entry, which states facts and leaves the decision to your policy — because your organisation is the only party entitled to say \"for us, this one is fine\".
23    #[serde(rename = "verdict", skip_serializing_if = "Option::is_none")]
24    pub verdict: Option<String>,
25}
26
27impl ReferenceOverrideIn {
28    pub fn new() -> ReferenceOverrideIn {
29        ReferenceOverrideIn {
30            key: None,
31            note: None,
32            verdict: None,
33        }
34    }
35}
36