/*
 * Artifact Keeper API
 *
 * Enterprise artifact registry supporting 45+ package formats.  ## Authentication  The JSON management API under `/api/v1/_*` accepts **API tokens only as `Authorization: Bearer <token>`**. This is the canonical scheme for programmatic access; JWTs issued by the login flow also use `Bearer`. HTTP Basic credentials on `/api/v1/_*` are validated *only* as a real `username:password` login — the password half is **not** retried as an API token. A request to `/api/v1/_*` that sends an API token in the password field of Basic auth therefore returns `401 AUTH_ERROR`; switch to `Authorization: Bearer <token>`.  Format (package-manager) endpoints such as `/v2/_*` (OCI), `/incus/_*`, `/debian/_*`, and the language registries are intentionally more permissive for client compatibility: in addition to Bearer, they accept HTTP **Basic** auth with the API token supplied in the *password* field (any username), matching the `pip` netrc / Artifactory-style `token:<api_token>` convention used by package managers that cannot send a Bearer header. This Basic-with-token fallback applies to format endpoints only, never to `/api/v1/_*`.
 *
 * The version of the OpenAPI document: 1.3.0
 * 
 * Generated by: https://openapi-generator.tech
 */

use crate::models;
use serde::{Deserialize, Serialize};

/// UpdatePolicyRequest : Partial-update payload for `PUT /security/policies/{id}`.  Every field is `Option<T>` so clients can send any subset of mutable columns; omitted fields leave the existing row value untouched. The previous shape required all of `name`, `max_severity`, `block_unscanned`, `block_on_fail`, `is_enabled` on every call. That was incompatible with the release-gate `scan-policy-crud` test (and external callers) which PATCH a subset like `{max_severity, is_enabled}`; under the strict shape the request was rejected as a 422 and the boolean toggle silently never took effect on a follow-up GET. See #1374.  For `min_staging_hours` / `max_artifact_age_days` the field is the inner nullable `i32`; \"not provided\" leaves the column untouched. Explicit `null` to clear those columns is not currently supported; the release gate only mutates the bool/enum fields, so the narrower semantics are sufficient and we avoid an ambiguous JSON contract.
#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)]
pub struct UpdatePolicyRequest {
    #[serde(rename = "block_on_fail", default, with = "::serde_with::rust::double_option", skip_serializing_if = "Option::is_none")]
    pub block_on_fail: Option<Option<bool>>,
    #[serde(rename = "block_unscanned", default, with = "::serde_with::rust::double_option", skip_serializing_if = "Option::is_none")]
    pub block_unscanned: Option<Option<bool>>,
    #[serde(rename = "is_enabled", default, with = "::serde_with::rust::double_option", skip_serializing_if = "Option::is_none")]
    pub is_enabled: Option<Option<bool>>,
    #[serde(rename = "max_artifact_age_days", default, with = "::serde_with::rust::double_option", skip_serializing_if = "Option::is_none")]
    pub max_artifact_age_days: Option<Option<i32>>,
    #[serde(rename = "max_severity", default, with = "::serde_with::rust::double_option", skip_serializing_if = "Option::is_none")]
    pub max_severity: Option<Option<String>>,
    #[serde(rename = "min_staging_hours", default, with = "::serde_with::rust::double_option", skip_serializing_if = "Option::is_none")]
    pub min_staging_hours: Option<Option<i32>>,
    #[serde(rename = "name", default, with = "::serde_with::rust::double_option", skip_serializing_if = "Option::is_none")]
    pub name: Option<Option<String>>,
    #[serde(rename = "require_signature", default, with = "::serde_with::rust::double_option", skip_serializing_if = "Option::is_none")]
    pub require_signature: Option<Option<bool>>,
}

impl UpdatePolicyRequest {
    /// Partial-update payload for `PUT /security/policies/{id}`.  Every field is `Option<T>` so clients can send any subset of mutable columns; omitted fields leave the existing row value untouched. The previous shape required all of `name`, `max_severity`, `block_unscanned`, `block_on_fail`, `is_enabled` on every call. That was incompatible with the release-gate `scan-policy-crud` test (and external callers) which PATCH a subset like `{max_severity, is_enabled}`; under the strict shape the request was rejected as a 422 and the boolean toggle silently never took effect on a follow-up GET. See #1374.  For `min_staging_hours` / `max_artifact_age_days` the field is the inner nullable `i32`; \"not provided\" leaves the column untouched. Explicit `null` to clear those columns is not currently supported; the release gate only mutates the bool/enum fields, so the narrower semantics are sufficient and we avoid an ambiguous JSON contract.
    pub fn new() -> UpdatePolicyRequest {
        UpdatePolicyRequest {
            block_on_fail: None,
            block_unscanned: None,
            is_enabled: None,
            max_artifact_age_days: None,
            max_severity: None,
            min_staging_hours: None,
            name: None,
            require_signature: None,
        }
    }
}

