docs: update docs (#916)
* fix: re-run script
* test: fix noxfile
diff --git a/docs/dyn/remotebuildexecution_v2.blobs.html b/docs/dyn/remotebuildexecution_v2.blobs.html
index ceb59b8..b40948e 100644
--- a/docs/dyn/remotebuildexecution_v2.blobs.html
+++ b/docs/dyn/remotebuildexecution_v2.blobs.html
@@ -182,16 +182,16 @@
#
# You can find out more about this error model and how to work with it in the
# [API Design Guide](https://cloud.google.com/apis/design/errors).
- "code": 42, # The status code, which should be an enum value of google.rpc.Code.
- "message": "A String", # A developer-facing error message, which should be in English. Any
- # user-facing error message should be localized and sent in the
- # google.rpc.Status.details field, or localized by the client.
"details": [ # A list of messages that carry the error details. There is a common set of
# message types for APIs to use.
{
"a_key": "", # Properties of the object. Contains field @type with type URL.
},
],
+ "code": 42, # The status code, which should be an enum value of google.rpc.Code.
+ "message": "A String", # A developer-facing error message, which should be in English. Any
+ # user-facing error message should be localized and sent in the
+ # google.rpc.Status.details field, or localized by the client.
},
"data": "A String", # The raw binary data.
"digest": { # A content digest. A digest for a given blob consists of the size of the blob # The digest to which this response corresponds.
@@ -326,6 +326,24 @@
# ContentAddressableStorage.BatchUpdateBlobs.
"responses": [ # The responses to the requests.
{ # A response corresponding to a single blob that the client tried to upload.
+ "status": { # The `Status` type defines a logical error model that is suitable for # The result of attempting to upload that blob.
+ # different programming environments, including REST APIs and RPC APIs. It is
+ # used by [gRPC](https://github.com/grpc). Each `Status` message contains
+ # three pieces of data: error code, error message, and error details.
+ #
+ # You can find out more about this error model and how to work with it in the
+ # [API Design Guide](https://cloud.google.com/apis/design/errors).
+ "details": [ # A list of messages that carry the error details. There is a common set of
+ # message types for APIs to use.
+ {
+ "a_key": "", # Properties of the object. Contains field @type with type URL.
+ },
+ ],
+ "code": 42, # The status code, which should be an enum value of google.rpc.Code.
+ "message": "A String", # A developer-facing error message, which should be in English. Any
+ # user-facing error message should be localized and sent in the
+ # google.rpc.Status.details field, or localized by the client.
+ },
"digest": { # A content digest. A digest for a given blob consists of the size of the blob # The blob digest to which this response corresponds.
# and its hash. The hash algorithm to use is defined by the server.
#
@@ -361,24 +379,6 @@
"hash": "A String", # The hash. In the case of SHA-256, it will always be a lowercase hex string
# exactly 64 characters long.
},
- "status": { # The `Status` type defines a logical error model that is suitable for # The result of attempting to upload that blob.
- # different programming environments, including REST APIs and RPC APIs. It is
- # used by [gRPC](https://github.com/grpc). Each `Status` message contains
- # three pieces of data: error code, error message, and error details.
- #
- # You can find out more about this error model and how to work with it in the
- # [API Design Guide](https://cloud.google.com/apis/design/errors).
- "code": 42, # The status code, which should be an enum value of google.rpc.Code.
- "message": "A String", # A developer-facing error message, which should be in English. Any
- # user-facing error message should be localized and sent in the
- # google.rpc.Status.details field, or localized by the client.
- "details": [ # A list of messages that carry the error details. There is a common set of
- # message types for APIs to use.
- {
- "a_key": "", # Properties of the object. Contains field @type with type URL.
- },
- ],
- },
},
],
}</pre>
@@ -626,6 +626,27 @@
# ]
# }
# ```
+ "symlinks": [ # The symlinks in the directory.
+ { # A `SymlinkNode` represents a symbolic link.
+ "nodeProperties": [ # The node properties of the SymlinkNode.
+ { # A single property for FileNodes,
+ # DirectoryNodes, and
+ # SymlinkNodes. The server is
+ # responsible for specifying the property `name`s that it accepts. If
+ # permitted by the server, the same `name` may occur multiple times.
+ "value": "A String", # The property value.
+ "name": "A String", # The property name.
+ },
+ ],
+ "name": "A String", # The name of the symlink.
+ "target": "A String", # The target path of the symlink. The path separator is a forward slash `/`.
+ # The target path can be relative to the parent directory of the symlink or
+ # it can be an absolute path starting with `/`. Support for absolute paths
+ # can be checked using the Capabilities
+ # API. The canonical form forbids the substrings `/./` and `//` in the target
+ # path. `..` components are allowed anywhere in the target path.
+ },
+ ],
"files": [ # The files in the directory.
{ # A `FileNode` represents a single file and associated metadata.
"nodeProperties": [ # The node properties of the FileNode.
@@ -732,27 +753,6 @@
"name": "A String", # The property name.
},
],
- "symlinks": [ # The symlinks in the directory.
- { # A `SymlinkNode` represents a symbolic link.
- "nodeProperties": [ # The node properties of the SymlinkNode.
- { # A single property for FileNodes,
- # DirectoryNodes, and
- # SymlinkNodes. The server is
- # responsible for specifying the property `name`s that it accepts. If
- # permitted by the server, the same `name` may occur multiple times.
- "value": "A String", # The property value.
- "name": "A String", # The property name.
- },
- ],
- "name": "A String", # The name of the symlink.
- "target": "A String", # The target path of the symlink. The path separator is a forward slash `/`.
- # The target path can be relative to the parent directory of the symlink or
- # it can be an absolute path starting with `/`. Support for absolute paths
- # can be checked using the Capabilities
- # API. The canonical form forbids the substrings `/./` and `//` in the target
- # path. `..` components are allowed anywhere in the target path.
- },
- ],
},
],
"nextPageToken": "A String", # If present, signifies that there are more results which the client can