Struct google_remotebuildexecution2::api::BuildBazelRemoteExecutionV2Directory

pub struct BuildBazelRemoteExecutionV2Directory {
    pub directories: Option<Vec<BuildBazelRemoteExecutionV2DirectoryNode>>,
    pub files: Option<Vec<BuildBazelRemoteExecutionV2FileNode>>,
    pub node_properties: Option<BuildBazelRemoteExecutionV2NodeProperties>,
    pub symlinks: Option<Vec<BuildBazelRemoteExecutionV2SymlinkNode>>,
}

A Directory represents a directory node in a file tree, containing zero or more children FileNodes, DirectoryNodes and SymlinkNodes. Each Node contains its name in the directory, either the digest of its content (either a file blob or a Directory proto) or a symlink target, as well as possibly some metadata about the file or directory. In order to ensure that two equivalent directory trees hash to the same value, the following restrictions MUST be obeyed when constructing a a Directory: * Every child in the directory must have a path of exactly one segment. Multiple levels of directory hierarchy may not be collapsed. * Each child in the directory must have a unique path segment (file name). Note that while the API itself is case-sensitive, the environment where the Action is executed may or may not be case-sensitive. That is, it is legal to call the API with a Directory that has both “Foo” and “foo” as children, but the Action may be rejected by the remote system upon execution. * The files, directories and symlinks in the directory must each be sorted in lexicographical order by path. The path strings must be sorted by code point, equivalently, by UTF-8 bytes. * The NodeProperties of files, directories, and symlinks must be sorted in lexicographical order by property name. A Directory that obeys the restrictions is said to be in canonical form. As an example, the following could be used for a file named bar and a directory named foo with an executable file named baz (hashes shortened for readability): json // (Directory proto) { files: [ { name: "bar", digest: { hash: "4a73bc9d03...", size: 65534 }, node_properties: [ { "name": "MTime", "value": "2017-01-15T01:30:15.01Z" } ] } ], directories: [ { name: "foo", digest: { hash: "4cf2eda940...", size: 43 } } ] } // (Directory proto with hash "4cf2eda940..." and size 43) { files: [ { name: "baz", digest: { hash: "b2c941073e...", size: 1294, }, is_executable: true } ] }

This type is not used in any activity, and only used as part of another schema.

Fields

directories: Option<Vec<BuildBazelRemoteExecutionV2DirectoryNode>>

The subdirectories in the directory.

files: Option<Vec<BuildBazelRemoteExecutionV2FileNode>>

The files in the directory.

node_properties: Option<BuildBazelRemoteExecutionV2NodeProperties>

no description provided

symlinks: Option<Vec<BuildBazelRemoteExecutionV2SymlinkNode>>

The symlinks in the directory.

Trait Implementations

impl Clone for BuildBazelRemoteExecutionV2Directory

fn clone(&self) -> BuildBazelRemoteExecutionV2Directory

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for BuildBazelRemoteExecutionV2Directory

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for BuildBazelRemoteExecutionV2Directory

fn default() -> BuildBazelRemoteExecutionV2Directory

Returns the “default value” for a type.

impl<'de> Deserialize<'de> for BuildBazelRemoteExecutionV2Directory

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>where
    __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl Serialize for BuildBazelRemoteExecutionV2Directory

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>where
    __S: Serializer,

Serialize this value into the given Serde serializer.

impl Part for BuildBazelRemoteExecutionV2Directory