chore: regens API reference docs (#889)
diff --git a/docs/dyn/remotebuildexecution_v2.actions.html b/docs/dyn/remotebuildexecution_v2.actions.html
index fd5fdc0..53723d3 100644
--- a/docs/dyn/remotebuildexecution_v2.actions.html
+++ b/docs/dyn/remotebuildexecution_v2.actions.html
@@ -75,11 +75,11 @@
<h1><a href="remotebuildexecution_v2.html">Remote Build Execution API</a> . <a href="remotebuildexecution_v2.actions.html">actions</a></h1>
<h2>Instance Methods</h2>
<p class="toc_element">
- <code><a href="#execute">execute(instanceName, body, x__xgafv=None)</a></code></p>
+ <code><a href="#execute">execute(instanceName, body=None, x__xgafv=None)</a></code></p>
<p class="firstline">Execute an action remotely.</p>
<h3>Method Details</h3>
<div class="method">
- <code class="details" id="execute">execute(instanceName, body, x__xgafv=None)</code>
+ <code class="details" id="execute">execute(instanceName, body=None, x__xgafv=None)</code>
<pre>Execute an action remotely.
In order to execute an action, the client must first upload all of the
@@ -150,24 +150,11 @@
storage, caches, etc.). The server MAY require use of this field to select
between them in an implementation-defined fashion, otherwise it can be
omitted. (required)
- body: object, The request body. (required)
+ body: object, The request body.
The object takes the form of:
{ # A request message for
# Execution.Execute.
- "resultsCachePolicy": { # A `ResultsCachePolicy` is used for fine-grained control over how action # An optional policy for the results of this execution in the remote cache.
- # The server will have a default policy if this is not provided.
- # This may be applied to both the ActionResult and the associated blobs.
- # outputs are stored in the CAS and Action Cache.
- "priority": 42, # The priority (relative importance) of this content in the overall cache.
- # Generally, a lower value means a longer retention time or other advantage,
- # but the interpretation of a given value is server-dependent. A priority of
- # 0 means a *default* value, decided by the server.
- #
- # The particular semantics of this field is up to the server. In particular,
- # every server will have their own supported range of priorities, and will
- # decide how these map into retention/eviction policy.
- },
"skipCacheLookup": True or False, # If true, the action will be executed even if its result is already
# present in the ActionCache.
# The execution is still allowed to be merged with other in-flight executions
@@ -181,10 +168,22 @@
# cache entries that reference outputs no longer available or that are
# poisoned in any way.
# If false, the result may be served from the action cache.
+ "resultsCachePolicy": { # A `ResultsCachePolicy` is used for fine-grained control over how action # An optional policy for the results of this execution in the remote cache.
+ # The server will have a default policy if this is not provided.
+ # This may be applied to both the ActionResult and the associated blobs.
+ # outputs are stored in the CAS and Action Cache.
+ "priority": 42, # The priority (relative importance) of this content in the overall cache.
+ # Generally, a lower value means a longer retention time or other advantage,
+ # but the interpretation of a given value is server-dependent. A priority of
+ # 0 means a *default* value, decided by the server.
+ #
+ # The particular semantics of this field is up to the server. In particular,
+ # every server will have their own supported range of priorities, and will
+ # decide how these map into retention/eviction policy.
+ },
"actionDigest": { # A content digest. A digest for a given blob consists of the size of the blob # The digest of the Action to
# execute.
- # and its hash. The hash algorithm to use is defined by the server, but servers
- # SHOULD use SHA-256.
+ # and its hash. The hash algorithm to use is defined by the server.
#
# 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