hanzo-client 8.5.156

Generated client for the Hanzo API — every service, one crate.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36

/*
 * 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 O11yPeriodStatusComponent {
    /// CurrentStatus is this component's own condition: \"full_outage\" for a service that did not answer its health probe at all.
    #[serde(rename = "current_status", skip_serializing_if = "Option::is_none")]
    pub current_status: Option<String>,
    /// ID is the component's stable handle, which on this platform IS the service name — there is no separate component registry to allocate ids from.
    #[serde(rename = "id", skip_serializing_if = "Option::is_none")]
    pub id: Option<String>,
    /// Name is the service as the fleet prober knows it (the `service` label on hanzo_service_up), so a reader can match a component to what is being probed.
    #[serde(rename = "name", skip_serializing_if = "Option::is_none")]
    pub name: Option<String>,
}

impl O11yPeriodStatusComponent {
    pub fn new() -> O11yPeriodStatusComponent {
        O11yPeriodStatusComponent {
            current_status: None,
            id: None,
            name: None,
        }
    }
}