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
37
38
39
40
41

/*
 * supports a RESTful API for the Libpod library
 *
 * This documentation describes the Podman v2.x+ RESTful API. It consists of a Docker-compatible API and a Libpod API providing support for Podman’s unique features such as pods.  To start the service and keep it running for 5,000 seconds (-t 0 runs forever):  podman system service -t 5000 &  You can then use cURL on the socket using requests documented below.  NOTE: if you install the package podman-docker, it will create a symbolic link for /run/docker.sock to /run/podman/podman.sock  NOTE: Some fields in the API response JSON are encoded as omitempty, which means that if said field has a zero value, they will not be encoded in the API response. This is a feature to help reduce the size of the JSON responses returned via the API.  NOTE: Due to the limitations of [go-swagger](https://github.com/go-swagger/go-swagger), some field values that have a complex type show up as null in the docs as well as in the API responses. This is because the zero value for the field type is null. The field description in the docs will state what type the field is expected to be for such cases.  See podman-system-service(1) for more information.  Quick Examples:  'podman info'  curl --unix-socket /run/podman/podman.sock http://d/v5.0.0/libpod/info  'podman pull quay.io/containers/podman'  curl -XPOST --unix-socket /run/podman/podman.sock -v 'http://d/v5.0.0/images/create?fromImage=quay.io%2Fcontainers%2Fpodman'  'podman list images'  curl --unix-socket /run/podman/podman.sock -v 'http://d/v5.0.0/libpod/images/json' | jq
 *
 * The version of the OpenAPI document: 5.0.0
 * Contact: podman@lists.podman.io
 * Generated by: https://openapi-generator.tech
 */

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

/// Info : Info contains information about the Volume as a whole as provided by the CSI storage plugin.
#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)]
pub struct Info {
    /// AccessibleTopolgoy is the topology this volume is actually accessible from.
    #[serde(rename = "AccessibleTopology", skip_serializing_if = "Option::is_none")]
    pub accessible_topology: Option<Vec<models::Topology>>,
    /// CapacityBytes is the capacity of the volume in bytes. A value of 0 indicates that the capacity is unknown.
    #[serde(rename = "CapacityBytes", skip_serializing_if = "Option::is_none")]
    pub capacity_bytes: Option<i64>,
    /// VolumeContext is the context originating from the CSI storage plugin when the Volume is created.
    #[serde(rename = "VolumeContext", skip_serializing_if = "Option::is_none")]
    pub volume_context: Option<std::collections::HashMap<String, String>>,
    /// VolumeID is the ID of the Volume as seen by the CSI storage plugin. This is distinct from the Volume's Swarm ID, which is the ID used by all of the Docker Engine to refer to the Volume. If this field is blank, then the Volume has not been successfully created yet.
    #[serde(rename = "VolumeID", skip_serializing_if = "Option::is_none")]
    pub volume_id: Option<String>,
}

impl Info {
    /// Info contains information about the Volume as a whole as provided by the CSI storage plugin.
    pub fn new() -> Info {
        Info {
            accessible_topology: None,
            capacity_bytes: None,
            volume_context: None,
            volume_id: None,
        }
    }
}