/*
* 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 EnvVarJson {
/// Key is the variable's name in the container, which must match `^[A-Za-z_][A-Za-z0-9_]*$`. For a sealed value it is also the last segment of the KMS ref, so it is what identifies the value across a round trip.
#[serde(rename = "key", skip_serializing_if = "Option::is_none")]
pub key: Option<String>,
/// Secret says the value lives in KMS and never in the database. A caller may only ADD secrecy: the server seals a value whose key or shape looks like a credential anyway (secretshape.go), so an entry can come back secret that was not sent that way.
#[serde(rename = "secret", skip_serializing_if = "Option::is_none")]
pub secret: Option<bool>,
/// Value is the plaintext, and it is WRITE-ONLY once the entry is secret: a sealed value reads back as \"\", and sending \"\" again KEEPS what is sealed rather than wiping it. Only a non-empty value seals a new one.
#[serde(rename = "value", skip_serializing_if = "Option::is_none")]
pub value: Option<String>,
}
impl EnvVarJson {
pub fn new() -> EnvVarJson {
EnvVarJson {
key: None,
secret: None,
value: None,
}
}
}