podman_autogen_api/models/cluster_volume.rs
1/*
2 * supports a RESTful API for the Libpod library
3 *
4 * 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
5 *
6 * The version of the OpenAPI document: 5.0.0
7 * Contact: podman@lists.podman.io
8 * Generated by: https://openapi-generator.tech
9 */
10
11use crate::models;
12use serde::{Deserialize, Serialize};
13
14/// ClusterVolume : ClusterVolume contains options and information specific to, and only present on, Swarm CSI cluster volumes.
15#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)]
16pub struct ClusterVolume {
17 #[serde(rename = "CreatedAt", skip_serializing_if = "Option::is_none")]
18 pub created_at: Option<String>,
19 /// ID is the Swarm ID of the volume. Because cluster volumes are Swarm objects, they have an ID, unlike non-cluster volumes, which only have a Name. This ID can be used to refer to the cluster volume.
20 #[serde(rename = "ID", skip_serializing_if = "Option::is_none")]
21 pub id: Option<String>,
22 #[serde(rename = "Info", skip_serializing_if = "Option::is_none")]
23 pub info: Option<Box<models::Info>>,
24 /// PublishStatus contains the status of the volume as it pertains to its publishing on Nodes.
25 #[serde(rename = "PublishStatus", skip_serializing_if = "Option::is_none")]
26 pub publish_status: Option<Vec<models::PublishStatus>>,
27 #[serde(rename = "Spec", skip_serializing_if = "Option::is_none")]
28 pub spec: Option<Box<models::ClusterVolumeSpec>>,
29 #[serde(rename = "UpdatedAt", skip_serializing_if = "Option::is_none")]
30 pub updated_at: Option<String>,
31 #[serde(rename = "Version", skip_serializing_if = "Option::is_none")]
32 pub version: Option<Box<models::Version>>,
33}
34
35impl ClusterVolume {
36 /// ClusterVolume contains options and information specific to, and only present on, Swarm CSI cluster volumes.
37 pub fn new() -> ClusterVolume {
38 ClusterVolume {
39 created_at: None,
40 id: None,
41 info: None,
42 publish_status: None,
43 spec: None,
44 updated_at: None,
45 version: None,
46 }
47 }
48}