chore: regens API reference docs (#889)
diff --git a/docs/dyn/cloudasset_v1beta1.folders.html b/docs/dyn/cloudasset_v1beta1.folders.html
index 44d1bb5..36f70ea 100644
--- a/docs/dyn/cloudasset_v1beta1.folders.html
+++ b/docs/dyn/cloudasset_v1beta1.folders.html
@@ -80,11 +80,11 @@
<p class="firstline">Returns the operations Resource.</p>
<p class="toc_element">
- <code><a href="#exportAssets">exportAssets(parent, body, x__xgafv=None)</a></code></p>
+ <code><a href="#exportAssets">exportAssets(parent, body=None, x__xgafv=None)</a></code></p>
<p class="firstline">Exports assets with time and resource types to a given Cloud Storage</p>
<h3>Method Details</h3>
<div class="method">
- <code class="details" id="exportAssets">exportAssets(parent, body, x__xgafv=None)</code>
+ <code class="details" id="exportAssets">exportAssets(parent, body=None, x__xgafv=None)</code>
<pre>Exports assets with time and resource types to a given Cloud Storage
location. The output format is newline-delimited JSON.
This API implements the google.longrunning.Operation API allowing you
@@ -95,7 +95,7 @@
organization number (such as "organizations/123"), a project ID (such as
"projects/my-project-id"), a project number (such as "projects/12345"), or
a folder number (such as "folders/123"). (required)
- body: object, The request body. (required)
+ body: object, The request body.
The object takes the form of:
{ # Export asset request.
@@ -106,13 +106,15 @@
# for all supported asset types.
"A String",
],
+ "contentType": "A String", # Asset content type. If not specified, no content but the asset name will be
+ # returned.
"outputConfig": { # Output configuration for export assets destination. # Required. Output configuration indicating where the results will be output
# to. All results will be in newline delimited JSON format.
"gcsDestination": { # A Cloud Storage location. # Destination on Cloud Storage.
"uriPrefix": "A String", # The uri prefix of all generated Cloud Storage objects. For example:
# "gs://bucket_name/object_name_prefix". Each object uri is in format:
- # "gs://bucket_name/object_name_prefix/<asset type>/<shard number> and only
- # contains assets for that type. <shard number> starts from 0. For example:
+ # "gs://bucket_name/object_name_prefix/<asset type>/<shard number> and only
+ # contains assets for that type. <shard number> starts from 0. For example:
# "gs://bucket_name/object_name_prefix/google.compute.disk/0" is the first
# shard of output objects containing all google.compute.disk assets.
# An INVALID_ARGUMENT error will be returned if file with the same name
@@ -124,8 +126,6 @@
# for more information.
},
},
- "contentType": "A String", # Asset content type. If not specified, no content but the asset name will be
- # returned.
"readTime": "A String", # Timestamp to take an asset snapshot. This can only be set to a timestamp
# between 2018-10-02 UTC (inclusive) and the current time. If not specified,
# the current time will be used. Due to delays in resource data collection
@@ -151,56 +151,11 @@
},
"error": { # The `Status` type defines a logical error model that is suitable for # The error result of the operation in case of failure or cancellation.
# different programming environments, including REST APIs and RPC APIs. It is
- # used by [gRPC](https://github.com/grpc). The error model is designed to be:
+ # used by [gRPC](https://github.com/grpc). Each `Status` message contains
+ # three pieces of data: error code, error message, and error details.
#
- # - Simple to use and understand for most users
- # - Flexible enough to meet unexpected needs
- #
- # # Overview
- #
- # The `Status` message contains three pieces of data: error code, error
- # message, and error details. The error code should be an enum value of
- # google.rpc.Code, but it may accept additional error codes if needed. The
- # error message should be a developer-facing English message that helps
- # developers *understand* and *resolve* the error. If a localized user-facing
- # error message is needed, put the localized message in the error details or
- # localize it in the client. The optional error details may contain arbitrary
- # information about the error. There is a predefined set of error detail types
- # in the package `google.rpc` that can be used for common error conditions.
- #
- # # Language mapping
- #
- # The `Status` message is the logical representation of the error model, but it
- # is not necessarily the actual wire format. When the `Status` message is
- # exposed in different client libraries and different wire protocols, it can be
- # mapped differently. For example, it will likely be mapped to some exceptions
- # in Java, but more likely mapped to some error codes in C.
- #
- # # Other uses
- #
- # The error model and the `Status` message can be used in a variety of
- # environments, either with or without APIs, to provide a
- # consistent developer experience across different environments.
- #
- # Example uses of this error model include:
- #
- # - Partial errors. If a service needs to return partial errors to the client,
- # it may embed the `Status` in the normal response to indicate the partial
- # errors.
- #
- # - Workflow errors. A typical workflow has multiple steps. Each step may
- # have a `Status` message for error reporting.
- #
- # - Batch operations. If a client uses batch request and batch response, the
- # `Status` message should be used directly inside batch response, one for
- # each error sub-response.
- #
- # - Asynchronous operations. If an API call embeds asynchronous operation
- # results in its response, the status of those operations should be
- # represented directly using the `Status` message.
- #
- # - Logging. If some API errors are stored in logs, the message `Status` could
- # be used directly after any stripping needed for security/privacy reasons.
+ # 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).
"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.
@@ -227,7 +182,7 @@
},
"name": "A String", # The server-assigned name, which is only unique within the same service that
# originally returns it. If you use the default HTTP mapping, the
- # `name` should have the format of `operations/some/unique/name`.
+ # `name` should be a resource name ending with `operations/{unique_id}`.
}</pre>
</div>