podman_autogen_api/models/
linux_device.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/// LinuxDevice : LinuxDevice represents the mknod information for a Linux special device file
15#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)]
16pub struct LinuxDevice {
17    /// The bits have the same definition on all systems, so that information about files can be moved from one system to another portably. Not all bits apply to all systems. The only required bit is [ModeDir] for directories.
18    #[serde(rename = "fileMode", skip_serializing_if = "Option::is_none")]
19    pub file_mode: Option<i32>,
20    /// Gid of the device.
21    #[serde(rename = "gid", skip_serializing_if = "Option::is_none")]
22    pub gid: Option<i32>,
23    /// Major is the device's major number.
24    #[serde(rename = "major", skip_serializing_if = "Option::is_none")]
25    pub major: Option<i64>,
26    /// Minor is the device's minor number.
27    #[serde(rename = "minor", skip_serializing_if = "Option::is_none")]
28    pub minor: Option<i64>,
29    /// Path to the device.
30    #[serde(rename = "path", skip_serializing_if = "Option::is_none")]
31    pub path: Option<String>,
32    /// Device type, block, char, etc.
33    #[serde(rename = "type", skip_serializing_if = "Option::is_none")]
34    pub r#type: Option<String>,
35    /// UID of the device.
36    #[serde(rename = "uid", skip_serializing_if = "Option::is_none")]
37    pub uid: Option<i32>,
38}
39
40impl LinuxDevice {
41    /// LinuxDevice represents the mknod information for a Linux special device file
42    pub fn new() -> LinuxDevice {
43        LinuxDevice {
44            file_mode: None,
45            gid: None,
46            major: None,
47            minor: None,
48            path: None,
49            r#type: None,
50            uid: None,
51        }
52    }
53}
podman_autogen_api/models/linux_device.rs

podman_autogen_api/models/
linux_device.rs
