Class: Google::Apis::RemotebuildexecutionV2::BuildBazelRemoteExecutionV2DirectoryNode
- Inherits:
-
Object
- Object
- Google::Apis::RemotebuildexecutionV2::BuildBazelRemoteExecutionV2DirectoryNode
- Includes:
- Core::Hashable, Core::JsonObjectSupport
- Defined in:
- generated/google/apis/remotebuildexecution_v2/classes.rb,
generated/google/apis/remotebuildexecution_v2/representations.rb,
generated/google/apis/remotebuildexecution_v2/representations.rb
Overview
A DirectoryNode
represents a child of a
Directory which is itself
a Directory
and its associated metadata.
Instance Attribute Summary collapse
-
#digest ⇒ Google::Apis::RemotebuildexecutionV2::BuildBazelRemoteExecutionV2Digest
A content digest.
-
#name ⇒ String
The name of the directory.
Instance Method Summary collapse
-
#initialize(**args) ⇒ BuildBazelRemoteExecutionV2DirectoryNode
constructor
A new instance of BuildBazelRemoteExecutionV2DirectoryNode.
-
#update!(**args) ⇒ Object
Update properties of this object.
Methods included from Core::JsonObjectSupport
Methods included from Core::Hashable
Constructor Details
#initialize(**args) ⇒ BuildBazelRemoteExecutionV2DirectoryNode
Returns a new instance of BuildBazelRemoteExecutionV2DirectoryNode.
1015 1016 1017 |
# File 'generated/google/apis/remotebuildexecution_v2/classes.rb', line 1015 def initialize(**args) update!(**args) end |
Instance Attribute Details
#digest ⇒ Google::Apis::RemotebuildexecutionV2::BuildBazelRemoteExecutionV2Digest
A content digest. A digest for a given blob consists of the size of the blob
and its hash. The hash algorithm to use is defined by the server, but servers
SHOULD use SHA-256.
The size is considered to be an integral part of the digest and cannot be
separated. That is, even if the hash
field is correctly specified but
size_bytes
is not, the server MUST reject the request.
The reason for including the size in the digest is as follows: in a great
many cases, the server needs to know the size of the blob it is about to work
with prior to starting an operation with it, such as flattening Merkle tree
structures or streaming it to a worker. Technically, the server could
implement a separate metadata store, but this results in a significantly more
complicated implementation as opposed to having the client specify the size
up-front (or storing the size along with the digest in every message where
digests are embedded). This does mean that the API leaks some implementation
details of (what we consider to be) a reasonable server implementation, but
we consider this to be a worthwhile tradeoff.
When a Digest
is used to refer to a proto message, it always refers to the
message in binary encoded form. To ensure consistent hashing, clients and
servers MUST ensure that they serialize messages according to the following
rules, even if there are alternate valid encodings for the same message:
- Fields are serialized in tag order.
- There are no unknown fields.
- There are no duplicate fields.
- Fields are serialized according to the default semantics for their type.
Most protocol buffer implementations will always follow these rules when
serializing, but care should be taken to avoid shortcuts. For instance,
concatenating two messages to merge them may produce duplicate fields.
Corresponds to the JSON property
digest
1008 1009 1010 |
# File 'generated/google/apis/remotebuildexecution_v2/classes.rb', line 1008 def digest @digest end |
#name ⇒ String
The name of the directory.
Corresponds to the JSON property name
1013 1014 1015 |
# File 'generated/google/apis/remotebuildexecution_v2/classes.rb', line 1013 def name @name end |
Instance Method Details
#update!(**args) ⇒ Object
Update properties of this object
1020 1021 1022 1023 |
# File 'generated/google/apis/remotebuildexecution_v2/classes.rb', line 1020 def update!(**args) @digest = args[:digest] if args.key?(:digest) @name = args[:name] if args.key?(:name) end |