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 RestartRef {
    /// App is the service's CR name, from the path. It must be a DNS-1123 label.
    #[serde(rename = "app", skip_serializing_if = "Option::is_none")]
    pub app: Option<String>,
    /// Env is REQUIRED and must be main, test or dev. A bare call does not default to production, which is what closes the fat-finger and confused-deputy hazard.  It carries no `validate:\"required\"`: the handler already refuses an empty env with the sentence that names the three values, and a validator tag would replace that sentence with a generic one. The requirement is stated here and enforced there, once.
    #[serde(rename = "env", skip_serializing_if = "Option::is_none")]
    pub env: Option<String>,
}

impl RestartRef {
    pub fn new() -> RestartRef {
        RestartRef {
            app: None,
            env: None,
        }
    }
}