Skip to content

chore: Update discovery artifacts #2421

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
26 commits
Select commit Hold shift + click to select a range
7c23925
chore: update docs/dyn/index.md
yoshi-automation Jun 25, 2024
fa0f740
feat(aiplatform): update the api
yoshi-automation Jun 25, 2024
5fa05a1
feat(alloydb): update the api
yoshi-automation Jun 25, 2024
e210698
feat(androidmanagement): update the api
yoshi-automation Jun 25, 2024
2159e56
feat(androidpublisher): update the api
yoshi-automation Jun 25, 2024
2552a87
feat(beyondcorp): update the api
yoshi-automation Jun 25, 2024
9911654
fix(bigquerydatatransfer): update the api
yoshi-automation Jun 25, 2024
6e68c87
fix(bigqueryreservation): update the api
yoshi-automation Jun 25, 2024
64f950c
feat(classroom): update the api
yoshi-automation Jun 25, 2024
d74083e
feat(containeranalysis): update the api
yoshi-automation Jun 25, 2024
c655e51
feat(datafusion): update the api
yoshi-automation Jun 25, 2024
c47274b
feat(dataproc): update the api
yoshi-automation Jun 25, 2024
f0f13cd
feat(dlp): update the api
yoshi-automation Jun 25, 2024
fd456c4
feat(firestore): update the api
yoshi-automation Jun 25, 2024
3388962
feat(games): update the api
yoshi-automation Jun 25, 2024
38b9107
feat(healthcare): update the api
yoshi-automation Jun 25, 2024
539b679
feat(iap): update the api
yoshi-automation Jun 25, 2024
c963397
feat(integrations): update the api
yoshi-automation Jun 25, 2024
83fdb4e
feat(jobs): update the api
yoshi-automation Jun 25, 2024
826d408
feat(monitoring): update the api
yoshi-automation Jun 25, 2024
d7b7ae5
feat(networkconnectivity): update the api
yoshi-automation Jun 25, 2024
bc1b1e6
feat(securitycenter): update the api
yoshi-automation Jun 25, 2024
025fe36
feat(vmmigration): update the api
yoshi-automation Jun 25, 2024
b672291
feat(walletobjects): update the api
yoshi-automation Jun 25, 2024
2303a5d
feat(workloadmanager): update the api
yoshi-automation Jun 25, 2024
4d17f53
chore(docs): Add new discovery artifacts and artifacts with minor upd…
yoshi-automation Jun 25, 2024
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
The table of contents is too big for display.
Diff view
Diff view
  •  
  •  
  •  
372 changes: 372 additions & 0 deletions docs/dyn/aiplatform_v1.projects.locations.html

Large diffs are not rendered by default.

Original file line number Diff line number Diff line change
Expand Up @@ -153,7 +153,6 @@ <h3>Method Details</h3>
&quot;a_key&quot;: &quot;A String&quot;,
},
&quot;name&quot;: &quot;A String&quot;, # Output only. Identifier. Resource name of a TuningJob. Format: `projects/{project}/locations/{location}/tuningJobs/{tuning_job}`
&quot;pipelineJob&quot;: &quot;A String&quot;, # Output only. The resource name of the PipelineJob associated with the TuningJob. Format: `projects/{project}/locations/{location}/pipelineJobs/{pipeline_job}`.
&quot;startTime&quot;: &quot;A String&quot;, # Output only. Time when the TuningJob for the first time entered the `JOB_STATE_RUNNING` state.
&quot;state&quot;: &quot;A String&quot;, # Output only. The detailed state of the job.
&quot;supervisedTuningSpec&quot;: { # Tuning Spec for Supervised Tuning. # Tuning Spec for Supervised Fine Tuning.
Expand Down Expand Up @@ -293,7 +292,6 @@ <h3>Method Details</h3>
&quot;a_key&quot;: &quot;A String&quot;,
},
&quot;name&quot;: &quot;A String&quot;, # Output only. Identifier. Resource name of a TuningJob. Format: `projects/{project}/locations/{location}/tuningJobs/{tuning_job}`
&quot;pipelineJob&quot;: &quot;A String&quot;, # Output only. The resource name of the PipelineJob associated with the TuningJob. Format: `projects/{project}/locations/{location}/pipelineJobs/{pipeline_job}`.
&quot;startTime&quot;: &quot;A String&quot;, # Output only. Time when the TuningJob for the first time entered the `JOB_STATE_RUNNING` state.
&quot;state&quot;: &quot;A String&quot;, # Output only. The detailed state of the job.
&quot;supervisedTuningSpec&quot;: { # Tuning Spec for Supervised Tuning. # Tuning Spec for Supervised Fine Tuning.
Expand Down Expand Up @@ -440,7 +438,6 @@ <h3>Method Details</h3>
&quot;a_key&quot;: &quot;A String&quot;,
},
&quot;name&quot;: &quot;A String&quot;, # Output only. Identifier. Resource name of a TuningJob. Format: `projects/{project}/locations/{location}/tuningJobs/{tuning_job}`
&quot;pipelineJob&quot;: &quot;A String&quot;, # Output only. The resource name of the PipelineJob associated with the TuningJob. Format: `projects/{project}/locations/{location}/pipelineJobs/{pipeline_job}`.
&quot;startTime&quot;: &quot;A String&quot;, # Output only. Time when the TuningJob for the first time entered the `JOB_STATE_RUNNING` state.
&quot;state&quot;: &quot;A String&quot;, # Output only. The detailed state of the job.
&quot;supervisedTuningSpec&quot;: { # Tuning Spec for Supervised Tuning. # Tuning Spec for Supervised Fine Tuning.
Expand Down Expand Up @@ -593,7 +590,6 @@ <h3>Method Details</h3>
&quot;a_key&quot;: &quot;A String&quot;,
},
&quot;name&quot;: &quot;A String&quot;, # Output only. Identifier. Resource name of a TuningJob. Format: `projects/{project}/locations/{location}/tuningJobs/{tuning_job}`
&quot;pipelineJob&quot;: &quot;A String&quot;, # Output only. The resource name of the PipelineJob associated with the TuningJob. Format: `projects/{project}/locations/{location}/pipelineJobs/{pipeline_job}`.
&quot;startTime&quot;: &quot;A String&quot;, # Output only. Time when the TuningJob for the first time entered the `JOB_STATE_RUNNING` state.
&quot;state&quot;: &quot;A String&quot;, # Output only. The detailed state of the job.
&quot;supervisedTuningSpec&quot;: { # Tuning Spec for Supervised Tuning. # Tuning Spec for Supervised Fine Tuning.
Expand Down
46 changes: 46 additions & 0 deletions docs/dyn/alloydb_v1.projects.locations.clusters.html
Original file line number Diff line number Diff line change
Expand Up @@ -114,6 +114,9 @@ <h2>Instance Methods</h2>
<p class="toc_element">
<code><a href="#restore">restore(parent, body=None, x__xgafv=None)</a></code></p>
<p class="firstline">Creates a new Cluster in a given project and location, with a volume restored from the provided source, either a backup ID or a point-in-time and a source cluster.</p>
<p class="toc_element">
<code><a href="#switchover">switchover(name, body=None, x__xgafv=None)</a></code></p>
<p class="firstline">Switches the role of PRIMARY and SECONDARY cluster without any data loss. This promotes the SECONDARY cluster to PRIMARY and sets up original PRIMARY cluster to replicate from this newly promoted cluster.</p>
<h3>Method Details</h3>
<div class="method">
<code class="details" id="close">close()</code>
Expand Down Expand Up @@ -1213,4 +1216,47 @@ <h3>Method Details</h3>
}</pre>
</div>

<div class="method">
<code class="details" id="switchover">switchover(name, body=None, x__xgafv=None)</code>
<pre>Switches the role of PRIMARY and SECONDARY cluster without any data loss. This promotes the SECONDARY cluster to PRIMARY and sets up original PRIMARY cluster to replicate from this newly promoted cluster.

Args:
name: string, Required. The name of the resource. For the required format, see the comment on the Cluster.name field (required)
body: object, The request body.
The object takes the form of:

{ # Message for switching over to a cluster
&quot;requestId&quot;: &quot;A String&quot;, # Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee that for at least 60 minutes after the first request. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
&quot;validateOnly&quot;: True or False, # Optional. If set, performs request validation (e.g. permission checks and any other type of validation), but do not actually execute the delete.
}

x__xgafv: string, V1 error format.
Allowed values
1 - v1 error format
2 - v2 error format

Returns:
An object of the form:

{ # This resource represents a long-running operation that is the result of a network API call.
&quot;done&quot;: True or False, # If the value is `false`, it means the operation is still in progress. If `true`, the operation is completed, and either `error` or `response` is available.
&quot;error&quot;: { # The `Status` type defines a logical error model that is suitable for 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). # The error result of the operation in case of failure or cancellation.
&quot;code&quot;: 42, # The status code, which should be an enum value of google.rpc.Code.
&quot;details&quot;: [ # A list of messages that carry the error details. There is a common set of message types for APIs to use.
{
&quot;a_key&quot;: &quot;&quot;, # Properties of the object. Contains field @type with type URL.
},
],
&quot;message&quot;: &quot;A String&quot;, # 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.
},
&quot;metadata&quot;: { # Service-specific metadata associated with the operation. It typically contains progress information and common metadata such as create time. Some services might not provide such metadata. Any method that returns a long-running operation should document the metadata type, if any.
&quot;a_key&quot;: &quot;&quot;, # Properties of the object. Contains field @type with type URL.
},
&quot;name&quot;: &quot;A String&quot;, # 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 be a resource name ending with `operations/{unique_id}`.
&quot;response&quot;: { # The normal, successful response of the operation. If the original method returns no data on success, such as `Delete`, the response is `google.protobuf.Empty`. If the original method is standard `Get`/`Create`/`Update`, the response should be the resource. For other methods, the response should have the type `XxxResponse`, where `Xxx` is the original method name. For example, if the original method name is `TakeSnapshot()`, the inferred response type is `TakeSnapshotResponse`.
&quot;a_key&quot;: &quot;&quot;, # Properties of the object. Contains field @type with type URL.
},
}</pre>
</div>

</body></html>
46 changes: 46 additions & 0 deletions docs/dyn/alloydb_v1alpha.projects.locations.clusters.html
Original file line number Diff line number Diff line change
Expand Up @@ -114,6 +114,9 @@ <h2>Instance Methods</h2>
<p class="toc_element">
<code><a href="#restore">restore(parent, body=None, x__xgafv=None)</a></code></p>
<p class="firstline">Creates a new Cluster in a given project and location, with a volume restored from the provided source, either a backup ID or a point-in-time and a source cluster.</p>
<p class="toc_element">
<code><a href="#switchover">switchover(name, body=None, x__xgafv=None)</a></code></p>
<p class="firstline">Switches the role of PRIMARY and SECONDARY cluster without any data loss. This promotes the SECONDARY cluster to PRIMARY and sets up original PRIMARY cluster to replicate from this newly promoted cluster.</p>
<h3>Method Details</h3>
<div class="method">
<code class="details" id="close">close()</code>
Expand Down Expand Up @@ -1273,4 +1276,47 @@ <h3>Method Details</h3>
}</pre>
</div>

<div class="method">
<code class="details" id="switchover">switchover(name, body=None, x__xgafv=None)</code>
<pre>Switches the role of PRIMARY and SECONDARY cluster without any data loss. This promotes the SECONDARY cluster to PRIMARY and sets up original PRIMARY cluster to replicate from this newly promoted cluster.

Args:
name: string, Required. The name of the resource. For the required format, see the comment on the Cluster.name field (required)
body: object, The request body.
The object takes the form of:

{ # Message for switching over to a cluster
&quot;requestId&quot;: &quot;A String&quot;, # Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee that for at least 60 minutes after the first request. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
&quot;validateOnly&quot;: True or False, # Optional. If set, performs request validation (e.g. permission checks and any other type of validation), but do not actually execute the delete.
}

x__xgafv: string, V1 error format.
Allowed values
1 - v1 error format
2 - v2 error format

Returns:
An object of the form:

{ # This resource represents a long-running operation that is the result of a network API call.
&quot;done&quot;: True or False, # If the value is `false`, it means the operation is still in progress. If `true`, the operation is completed, and either `error` or `response` is available.
&quot;error&quot;: { # The `Status` type defines a logical error model that is suitable for 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). # The error result of the operation in case of failure or cancellation.
&quot;code&quot;: 42, # The status code, which should be an enum value of google.rpc.Code.
&quot;details&quot;: [ # A list of messages that carry the error details. There is a common set of message types for APIs to use.
{
&quot;a_key&quot;: &quot;&quot;, # Properties of the object. Contains field @type with type URL.
},
],
&quot;message&quot;: &quot;A String&quot;, # 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.
},
&quot;metadata&quot;: { # Service-specific metadata associated with the operation. It typically contains progress information and common metadata such as create time. Some services might not provide such metadata. Any method that returns a long-running operation should document the metadata type, if any.
&quot;a_key&quot;: &quot;&quot;, # Properties of the object. Contains field @type with type URL.
},
&quot;name&quot;: &quot;A String&quot;, # 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 be a resource name ending with `operations/{unique_id}`.
&quot;response&quot;: { # The normal, successful response of the operation. If the original method returns no data on success, such as `Delete`, the response is `google.protobuf.Empty`. If the original method is standard `Get`/`Create`/`Update`, the response should be the resource. For other methods, the response should have the type `XxxResponse`, where `Xxx` is the original method name. For example, if the original method name is `TakeSnapshot()`, the inferred response type is `TakeSnapshotResponse`.
&quot;a_key&quot;: &quot;&quot;, # Properties of the object. Contains field @type with type URL.
},
}</pre>
</div>

</body></html>
46 changes: 46 additions & 0 deletions docs/dyn/alloydb_v1beta.projects.locations.clusters.html
Original file line number Diff line number Diff line change
Expand Up @@ -114,6 +114,9 @@ <h2>Instance Methods</h2>
<p class="toc_element">
<code><a href="#restore">restore(parent, body=None, x__xgafv=None)</a></code></p>
<p class="firstline">Creates a new Cluster in a given project and location, with a volume restored from the provided source, either a backup ID or a point-in-time and a source cluster.</p>
<p class="toc_element">
<code><a href="#switchover">switchover(name, body=None, x__xgafv=None)</a></code></p>
<p class="firstline">Switches the role of PRIMARY and SECONDARY cluster without any data loss. This promotes the SECONDARY cluster to PRIMARY and sets up original PRIMARY cluster to replicate from this newly promoted cluster.</p>
<h3>Method Details</h3>
<div class="method">
<code class="details" id="close">close()</code>
Expand Down Expand Up @@ -1267,4 +1270,47 @@ <h3>Method Details</h3>
}</pre>
</div>

<div class="method">
<code class="details" id="switchover">switchover(name, body=None, x__xgafv=None)</code>
<pre>Switches the role of PRIMARY and SECONDARY cluster without any data loss. This promotes the SECONDARY cluster to PRIMARY and sets up original PRIMARY cluster to replicate from this newly promoted cluster.

Args:
name: string, Required. The name of the resource. For the required format, see the comment on the Cluster.name field (required)
body: object, The request body.
The object takes the form of:

{ # Message for switching over to a cluster
&quot;requestId&quot;: &quot;A String&quot;, # Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee that for at least 60 minutes after the first request. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
&quot;validateOnly&quot;: True or False, # Optional. If set, performs request validation (e.g. permission checks and any other type of validation), but do not actually execute the delete.
}

x__xgafv: string, V1 error format.
Allowed values
1 - v1 error format
2 - v2 error format

Returns:
An object of the form:

{ # This resource represents a long-running operation that is the result of a network API call.
&quot;done&quot;: True or False, # If the value is `false`, it means the operation is still in progress. If `true`, the operation is completed, and either `error` or `response` is available.
&quot;error&quot;: { # The `Status` type defines a logical error model that is suitable for 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). # The error result of the operation in case of failure or cancellation.
&quot;code&quot;: 42, # The status code, which should be an enum value of google.rpc.Code.
&quot;details&quot;: [ # A list of messages that carry the error details. There is a common set of message types for APIs to use.
{
&quot;a_key&quot;: &quot;&quot;, # Properties of the object. Contains field @type with type URL.
},
],
&quot;message&quot;: &quot;A String&quot;, # 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.
},
&quot;metadata&quot;: { # Service-specific metadata associated with the operation. It typically contains progress information and common metadata such as create time. Some services might not provide such metadata. Any method that returns a long-running operation should document the metadata type, if any.
&quot;a_key&quot;: &quot;&quot;, # Properties of the object. Contains field @type with type URL.
},
&quot;name&quot;: &quot;A String&quot;, # 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 be a resource name ending with `operations/{unique_id}`.
&quot;response&quot;: { # The normal, successful response of the operation. If the original method returns no data on success, such as `Delete`, the response is `google.protobuf.Empty`. If the original method is standard `Get`/`Create`/`Update`, the response should be the resource. For other methods, the response should have the type `XxxResponse`, where `Xxx` is the original method name. For example, if the original method name is `TakeSnapshot()`, the inferred response type is `TakeSnapshotResponse`.
&quot;a_key&quot;: &quot;&quot;, # Properties of the object. Contains field @type with type URL.
},
}</pre>
</div>

</body></html>
Loading