/*
* 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 SettingsReq {
/// Config is the product's non-secret configuration, stored verbatim. Bounded at 64 KiB once serialized. Omit it to store an empty object.
#[serde(rename = "config", skip_serializing_if = "Option::is_none")]
pub config: Option<std::collections::HashMap<String, serde_json::Value>>,
/// Product is the catalog slug, from the PATH. zip binds the path last, so the URL names the product being written whatever a body field claims.
#[serde(rename = "product", skip_serializing_if = "Option::is_none")]
pub product: Option<String>,
/// Secrets are the secret fields, by name. Each VALUE is sealed into KMS and never reaches this deployment's database; a value that is empty or equal to the mask the read path returns means \"unchanged\" and is skipped, so a console round-trip cannot blank a stored secret. A key must match ^[a-z0-9][a-z0-9._-]{0,62}$, a value is bounded at 8 KiB, and an org may hold at most 64 secret fields per product.
#[serde(rename = "secrets", skip_serializing_if = "Option::is_none")]
pub secrets: Option<std::collections::HashMap<String, String>>,
}
impl SettingsReq {
pub fn new() -> SettingsReq {
SettingsReq {
config: None,
product: None,
secrets: None,
}
}
}