mirror of
https://github.com/OMGeeky/google-apis-rs.git
synced 2026-02-23 15:49:49 +01:00
Update documentation
This commit is contained in:
Sebastian Thiel
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href="." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href="." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -155,6 +155,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="projects_instances-clusters-partial-update-cluster/">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="projects_instances-clusters-update/">Instances Clusters Update</a>
|
||||
|
||||
@@ -330,7 +335,7 @@ capabilities. Errors will be printed to standard error, and cause the program's
|
||||
|
||||
<p>Find the source code <a href="https://github.com/Byron/google-apis-rs/tree/main/gen/bigtableadmin2-cli">on github</a>.</p>
|
||||
<h1 id="usage">Usage</h1>
|
||||
<p>This documentation was generated from the <em>Bigtable Admin</em> API at revision <em>20210323</em>. The CLI is at version <em>2.0.4</em>.</p>
|
||||
<p>This documentation was generated from the <em>Bigtable Admin</em> API at revision <em>20220222</em>. The CLI is at version <em>3.0.0</em>.</p>
|
||||
<pre><code class="bash">bigtableadmin2 [options]
|
||||
operations
|
||||
cancel <name> [-p <v>]... [-o <out>]
|
||||
@@ -355,6 +360,7 @@ capabilities. Errors will be printed to standard error, and cause the program's
|
||||
instances-clusters-delete <name> [-p <v>]... [-o <out>]
|
||||
instances-clusters-get <name> [-p <v>]... [-o <out>]
|
||||
instances-clusters-list <parent> [-p <v>]... [-o <out>]
|
||||
instances-clusters-partial-update-cluster <name> (-r <kv>)... [-p <v>]... [-o <out>]
|
||||
instances-clusters-update <name> (-r <kv>)... [-p <v>]... [-o <out>]
|
||||
instances-create <parent> (-r <kv>)... [-p <v>]... [-o <out>]
|
||||
instances-delete <name> [-p <v>]... [-o <out>]
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Cancel - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Cancel - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -171,6 +171,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Delete - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Delete - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -171,6 +171,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Get - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Get - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -171,6 +171,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Projects Operations List - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Projects Operations List - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -174,6 +174,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances App Profiles Create - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances App Profiles Create - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -179,6 +179,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
@@ -362,6 +367,8 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<pre><code>AppProfile:
|
||||
description: string
|
||||
etag: string
|
||||
multi-cluster-routing-use-any:
|
||||
cluster-ids: [string]
|
||||
name: string
|
||||
single-cluster-routing:
|
||||
allow-transactional-writes: boolean
|
||||
@@ -379,15 +386,24 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<li>Strongly validated etag for optimistic concurrency control. Preserve the value returned from <code>GetAppProfile</code> when calling <code>UpdateAppProfile</code> to fail the request if there has been a modification in the mean time. The <code>update_mask</code> of the request need not include <code>etag</code> for this protection to apply. See <a href="https://en.wikipedia.org/wiki/HTTP_ETag">Wikipedia</a> and <a href="https://tools.ietf.org/html/rfc7232#section-2.3">RFC 7232</a> for more details.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>name=no</code><ul>
|
||||
<li>
|
||||
<p><code>multi-cluster-routing-use-any cluster-ids=no</code></p>
|
||||
<ul>
|
||||
<li>The set of clusters to route to. The order is ignored; clusters will be tried in order of distance. If left empty, all clusters are eligible.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. name=ipsum</code></p>
|
||||
<ul>
|
||||
<li>The unique name of the app profile. Values are of the form <code>projects/{project}/instances/{instance}/appProfiles/_a-zA-Z0-9*</code>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>single-cluster-routing allow-transactional-writes=true</code><ul>
|
||||
<li><code>single-cluster-routing allow-transactional-writes=false</code><ul>
|
||||
<li>Whether or not <code>CheckAndMutateRow</code> and <code>ReadModifyWriteRow</code> requests are allowed by this app profile. It is unsafe to send these requests to the same table/row/column in multiple clusters.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>cluster-id=voluptua.</code><ul>
|
||||
<li><code>cluster-id=amet.</code><ul>
|
||||
<li>The cluster to which read/write requests should be routed.</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances App Profiles Delete - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances App Profiles Delete - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -174,6 +174,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances App Profiles Get - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances App Profiles Get - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -171,6 +171,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances App Profiles List - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances App Profiles List - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -174,6 +174,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances App Profiles Patch - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances App Profiles Patch - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -179,6 +179,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
@@ -362,6 +367,8 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<pre><code>AppProfile:
|
||||
description: string
|
||||
etag: string
|
||||
multi-cluster-routing-use-any:
|
||||
cluster-ids: [string]
|
||||
name: string
|
||||
single-cluster-routing:
|
||||
allow-transactional-writes: boolean
|
||||
@@ -371,15 +378,24 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r . description=at</code><ul>
|
||||
<li><code>-r . description=takimata</code><ul>
|
||||
<li>Long form description of the use case for this AppProfile.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>etag=sanctus</code><ul>
|
||||
<li><code>etag=amet.</code><ul>
|
||||
<li>Strongly validated etag for optimistic concurrency control. Preserve the value returned from <code>GetAppProfile</code> when calling <code>UpdateAppProfile</code> to fail the request if there has been a modification in the mean time. The <code>update_mask</code> of the request need not include <code>etag</code> for this protection to apply. See <a href="https://en.wikipedia.org/wiki/HTTP_ETag">Wikipedia</a> and <a href="https://tools.ietf.org/html/rfc7232#section-2.3">RFC 7232</a> for more details.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>name=sed</code><ul>
|
||||
<li>
|
||||
<p><code>multi-cluster-routing-use-any cluster-ids=duo</code></p>
|
||||
<ul>
|
||||
<li>The set of clusters to route to. The order is ignored; clusters will be tried in order of distance. If left empty, all clusters are eligible.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. name=ipsum</code></p>
|
||||
<ul>
|
||||
<li>The unique name of the app profile. Values are of the form <code>projects/{project}/instances/{instance}/appProfiles/_a-zA-Z0-9*</code>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -387,7 +403,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<li>Whether or not <code>CheckAndMutateRow</code> and <code>ReadModifyWriteRow</code> requests are allowed by this app profile. It is unsafe to send these requests to the same table/row/column in multiple clusters.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>cluster-id=amet.</code><ul>
|
||||
<li><code>cluster-id=lorem</code><ul>
|
||||
<li>The cluster to which read/write requests should be routed.</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Clusters Backups Create - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances Clusters Backups Create - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -179,6 +179,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
@@ -377,43 +382,43 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r .encryption-info.encryption-status code=81</code><ul>
|
||||
<li><code>-r .encryption-info.encryption-status code=89</code><ul>
|
||||
<li>The status code, which should be an enum value of google.rpc.Code.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>message=ipsum</code></p>
|
||||
<p><code>message=eos</code></p>
|
||||
<ul>
|
||||
<li>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.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. encryption-type=gubergren</code></p>
|
||||
<p><code>.. encryption-type=dolor</code></p>
|
||||
<ul>
|
||||
<li>Output only. The type of encryption used to protect this resource.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>kms-key-version=lorem</code></p>
|
||||
<p><code>kms-key-version=ea</code></p>
|
||||
<ul>
|
||||
<li>Output only. The version of the Cloud KMS key specified in the parent cluster that is in use for the data underlying this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. end-time=gubergren</code></p>
|
||||
<p><code>.. end-time=ipsum</code></p>
|
||||
<ul>
|
||||
<li>Output only. <code>end_time</code> is the time that the backup was finished. The row data in the backup will be no newer than this timestamp.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>expire-time=eos</code><ul>
|
||||
<li><code>expire-time=invidunt</code><ul>
|
||||
<li>Required. The expiration time of the backup, with microseconds granularity that must be at least 6 hours and at most 30 days from the time the request is received. Once the <code>expire_time</code> has passed, Cloud Bigtable will delete the backup and free the resources used by the backup.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>name=dolor</code><ul>
|
||||
<li><code>name=amet</code><ul>
|
||||
<li>A globally unique identifier for the backup which cannot be changed. Values are of the form <code>projects/{project}/instances/{instance}/clusters/{cluster}/ backups/_a-zA-Z0-9*</code> The final segment of the name must be between 1 and 50 characters in length. The backup is stored in the cluster identified by the prefix of the backup name of the form <code>projects/{project}/instances/{instance}/clusters/{cluster}</code>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>size-bytes=ea</code><ul>
|
||||
<li><code>size-bytes=duo</code><ul>
|
||||
<li>Output only. Size of the backup in bytes.</li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -421,11 +426,11 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<li>Required. Immutable. Name of the table from which this backup was created. This needs to be in the same instance as the backup. Values are of the form <code>projects/{project}/instances/{instance}/tables/{source_table}</code>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>start-time=invidunt</code><ul>
|
||||
<li><code>start-time=sed</code><ul>
|
||||
<li>Output only. <code>start_time</code> is the time that the backup was started (i.e. approximately the time the CreateBackup request is received). The row data in this backup will be no older than this timestamp.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>state=amet</code><ul>
|
||||
<li><code>state=ut</code><ul>
|
||||
<li>Output only. The current state of the backup.</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Clusters Backups Delete - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances Clusters Backups Delete - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -171,6 +171,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Clusters Backups Get Iam Policy - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances Clusters Backups Get Iam Policy - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -176,6 +176,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
@@ -363,8 +368,8 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r .options requested-policy-version=81</code><ul>
|
||||
<li>Optional. The policy format version to be returned. Valid values are 0, 1, and 3. Requests specifying an invalid value will be rejected. Requests for policies with any conditional bindings must specify version 3. Policies without any conditional bindings may specify any valid value or leave the field unset. To learn which resources support conditions in their IAM policies, see the <a href="https://cloud.google.com/iam/help/conditions/resource-policies">IAM documentation</a>.</li>
|
||||
<li><code>-r .options requested-policy-version=89</code><ul>
|
||||
<li>Optional. The maximum policy version that will be used to format the policy. Valid values are 0, 1, and 3. Requests specifying an invalid value will be rejected. Requests for policies with any conditional role bindings must specify version 3. Policies with no conditional role bindings may specify any valid value or leave the field unset. The policy in the response might use the policy version that you specified, or it might use a lower policy version. For example, if you specify version 3, but the policy has no conditional role bindings, the response uses version 1. To learn which resources support conditions in their IAM policies, see the <a href="https://cloud.google.com/iam/help/conditions/resource-policies">IAM documentation</a>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Clusters Backups Get - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances Clusters Backups Get - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -171,6 +171,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Clusters Backups List - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances Clusters Backups List - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -174,6 +174,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Clusters Backups Patch - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances Clusters Backups Patch - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -179,6 +179,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
@@ -377,55 +382,55 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r .encryption-info.encryption-status code=51</code><ul>
|
||||
<li><code>-r .encryption-info.encryption-status code=85</code><ul>
|
||||
<li>The status code, which should be an enum value of google.rpc.Code.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>message=sed</code></p>
|
||||
<p><code>message=est</code></p>
|
||||
<ul>
|
||||
<li>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.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. encryption-type=ut</code></p>
|
||||
<p><code>.. encryption-type=ipsum</code></p>
|
||||
<ul>
|
||||
<li>Output only. The type of encryption used to protect this resource.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>kms-key-version=gubergren</code></p>
|
||||
<p><code>kms-key-version=ipsum</code></p>
|
||||
<ul>
|
||||
<li>Output only. The version of the Cloud KMS key specified in the parent cluster that is in use for the data underlying this table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. end-time=rebum.</code></p>
|
||||
<p><code>.. end-time=est</code></p>
|
||||
<ul>
|
||||
<li>Output only. <code>end_time</code> is the time that the backup was finished. The row data in the backup will be no newer than this timestamp.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>expire-time=est</code><ul>
|
||||
<li><code>expire-time=gubergren</code><ul>
|
||||
<li>Required. The expiration time of the backup, with microseconds granularity that must be at least 6 hours and at most 30 days from the time the request is received. Once the <code>expire_time</code> has passed, Cloud Bigtable will delete the backup and free the resources used by the backup.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>name=ipsum</code><ul>
|
||||
<li><code>name=ea</code><ul>
|
||||
<li>A globally unique identifier for the backup which cannot be changed. Values are of the form <code>projects/{project}/instances/{instance}/clusters/{cluster}/ backups/_a-zA-Z0-9*</code> The final segment of the name must be between 1 and 50 characters in length. The backup is stored in the cluster identified by the prefix of the backup name of the form <code>projects/{project}/instances/{instance}/clusters/{cluster}</code>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>size-bytes=ipsum</code><ul>
|
||||
<li><code>size-bytes=dolor</code><ul>
|
||||
<li>Output only. Size of the backup in bytes.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>source-table=est</code><ul>
|
||||
<li><code>source-table=lorem</code><ul>
|
||||
<li>Required. Immutable. Name of the table from which this backup was created. This needs to be in the same instance as the backup. Values are of the form <code>projects/{project}/instances/{instance}/tables/{source_table}</code>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>start-time=gubergren</code><ul>
|
||||
<li><code>start-time=eos</code><ul>
|
||||
<li>Output only. <code>start_time</code> is the time that the backup was started (i.e. approximately the time the CreateBackup request is received). The row data in this backup will be no older than this timestamp.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>state=ea</code><ul>
|
||||
<li><code>state=labore</code><ul>
|
||||
<li>Output only. The current state of the backup.</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Clusters Backups Set Iam Policy - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances Clusters Backups Set Iam Policy - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -176,6 +176,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
@@ -365,18 +370,18 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r .policy etag=dolor</code><ul>
|
||||
<li><code>-r .policy etag=sed</code><ul>
|
||||
<li><code>etag</code> is used for optimistic concurrency control as a way to help prevent simultaneous updates of a policy from overwriting each other. It is strongly suggested that systems make use of the <code>etag</code> in the read-modify-write cycle to perform policy updates in order to avoid race conditions: An <code>etag</code> is returned in the response to <code>getIamPolicy</code>, and systems are expected to put that etag in the request to <code>setIamPolicy</code> to ensure that their change will be applied to the same version of the policy. <strong>Important:</strong> If you use IAM Conditions, you must include the <code>etag</code> field whenever you call <code>setIamPolicy</code>. If you omit this field, then IAM allows you to overwrite a version <code>3</code> policy with a version <code>1</code> policy, and all of the conditions in the version <code>3</code> policy are lost.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>version=45</code></p>
|
||||
<p><code>version=31</code></p>
|
||||
<ul>
|
||||
<li>Specifies the format of the policy. Valid values are <code>0</code>, <code>1</code>, and <code>3</code>. Requests that specify an invalid value are rejected. Any operation that affects conditional role bindings must specify version <code>3</code>. This requirement applies to the following operations: * Getting a policy that includes a conditional role binding * Adding a conditional role binding to a policy * Changing a conditional role binding in a policy * Removing any role binding, with or without a condition, from a policy that includes conditions <strong>Important:</strong> If you use IAM Conditions, you must include the <code>etag</code> field whenever you call <code>setIamPolicy</code>. If you omit this field, then IAM allows you to overwrite a version <code>3</code> policy with a version <code>1</code> policy, and all of the conditions in the version <code>3</code> policy are lost. If a policy does not include any conditions, operations on that policy may specify any valid version or leave the field unset. To learn which resources support conditions in their IAM policies, see the <a href="https://cloud.google.com/iam/help/conditions/resource-policies">IAM documentation</a>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. update-mask=eos</code></p>
|
||||
<p><code>.. update-mask=sed</code></p>
|
||||
<ul>
|
||||
<li>OPTIONAL: A FieldMask specifying which fields of the policy to modify. Only the fields in the mask will be modified. If no mask is provided, the following default mask is used: <code>paths: &#34;bindings, etag&#34;</code></li>
|
||||
</ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Clusters Backups Test Iam Permissions - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances Clusters Backups Test Iam Permissions - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -176,6 +176,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
@@ -362,7 +367,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r . permissions=labore</code><ul>
|
||||
<li><code>-r . permissions=no</code><ul>
|
||||
<li>The set of permissions to check for the <code>resource</code>. Permissions with wildcards (such as '<em>' or 'storage.</em>') are not allowed. For more information see <a href="https://cloud.google.com/iam/docs/overview#permissions">IAM Overview</a>.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Clusters Create - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances Clusters Create - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -179,6 +179,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
@@ -335,7 +340,7 @@
|
||||
</div>
|
||||
<div role="main">
|
||||
<div class="section">
|
||||
<p>Creates a cluster within an instance.</p>
|
||||
<p>Creates a cluster within an instance. Note that exactly one of Cluster.serve_nodes and Cluster.cluster_config.cluster_autoscaling_config can be set. If serve_nodes is set to non-zero, then the cluster is manually scaled. If cluster_config.cluster_autoscaling_config is non-empty, then autoscaling is enabled.</p>
|
||||
<h1 id="scopes">Scopes</h1>
|
||||
<p>You will need authorization for at least one of the following scopes to make a valid call:</p>
|
||||
<ul>
|
||||
@@ -360,6 +365,13 @@ You can set the scope for this method like this: <code>bigtableadmin2 --scope &l
|
||||
In the latter case it is advised to set the field-cursor to the data-structure's field to specify values more concisely.</p>
|
||||
<p>For example, a structure like this:</p>
|
||||
<pre><code>Cluster:
|
||||
cluster-config:
|
||||
cluster-autoscaling-config:
|
||||
autoscaling-limits:
|
||||
max-serve-nodes: integer
|
||||
min-serve-nodes: integer
|
||||
autoscaling-targets:
|
||||
cpu-utilization-percent: integer
|
||||
default-storage-type: string
|
||||
encryption-config:
|
||||
kms-key-name: string
|
||||
@@ -372,31 +384,49 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r . default-storage-type=sed</code><ul>
|
||||
<li><code>-r .cluster-config.cluster-autoscaling-config.autoscaling-limits max-serve-nodes=86</code><ul>
|
||||
<li>Required. Maximum number of nodes to scale up to.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>min-serve-nodes=88</code></p>
|
||||
<ul>
|
||||
<li>Required. Minimum number of nodes to scale down to.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..autoscaling-targets cpu-utilization-percent=77</code></p>
|
||||
<ul>
|
||||
<li>The cpu utilization that the Autoscaler should be trying to achieve. This number is on a scale from 0 (no utilization) to 100 (total utilization), and is limited between 10 and 80.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.... default-storage-type=sed</code></p>
|
||||
<ul>
|
||||
<li>Immutable. The type of storage used by this cluster to serve its parent instance's tables, unless explicitly overridden.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>encryption-config kms-key-name=duo</code></p>
|
||||
<p><code>encryption-config kms-key-name=et</code></p>
|
||||
<ul>
|
||||
<li>Describes the Cloud KMS encryption key that will be used to protect the destination Bigtable cluster. The requirements for this key are: 1) The Cloud Bigtable service account associated with the project that contains this cluster must be granted the <code>cloudkms.cryptoKeyEncrypterDecrypter</code> role on the CMEK key. 2) Only regional keys can be used and the region of the CMEK key must match the region of the cluster. 3) All clusters within an instance must use the same CMEK key. Values are of the form <code>projects/{project}/locations/{location}/keyRings/{keyring}/cryptoKeys/{key}</code></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. location=sed</code></p>
|
||||
<p><code>.. location=et</code></p>
|
||||
<ul>
|
||||
<li>Immutable. The location where this cluster's nodes and storage reside. For best performance, clients should be located as close as possible to this cluster. Currently only zones are supported, so values should be of the form <code>projects/{project}/locations/{zone}</code>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>name=no</code><ul>
|
||||
<li><code>name=vero</code><ul>
|
||||
<li>The unique name of the cluster. Values are of the form <code>projects/{project}/instances/{instance}/clusters/a-z*</code>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>serve-nodes=86</code><ul>
|
||||
<li>Required. The number of nodes allocated to this cluster. More nodes enable higher throughput and more consistent performance.</li>
|
||||
<li><code>serve-nodes=70</code><ul>
|
||||
<li>The number of nodes allocated to this cluster. More nodes enable higher throughput and more consistent performance.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>state=kasd</code><ul>
|
||||
<li><code>state=sed</code><ul>
|
||||
<li>Output only. The current state of the cluster.</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Clusters Delete - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances Clusters Delete - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -171,6 +171,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Clusters Get - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances Clusters Get - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -171,6 +171,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Clusters List - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances Clusters List - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -174,6 +174,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
@@ -449,7 +454,7 @@ or more key-value-pairs, and is called like this <code>-p k1=v1 k2=v2</code> eve
|
||||
|
||||
<div class="rst-footer-buttons" role="navigation" aria-label="footer navigation">
|
||||
|
||||
<a href="../projects_instances-clusters-update" class="btn btn-neutral float-right" title="Instances Clusters Update"/>Next <span class="icon icon-circle-arrow-right"></span></a>
|
||||
<a href="../projects_instances-clusters-partial-update-cluster" class="btn btn-neutral float-right" title="Instances Clusters Partial Update Cluster"/>Next <span class="icon icon-circle-arrow-right"></span></a>
|
||||
|
||||
|
||||
<a href="../projects_instances-clusters-get" class="btn btn-neutral" title="Instances Clusters Get"><span class="icon icon-circle-arrow-left"></span> Previous</a>
|
||||
@@ -481,7 +486,7 @@ or more key-value-pairs, and is called like this <code>-p k1=v1 k2=v2</code> eve
|
||||
<a class="icon icon-github" style="float: left; color: #fcfcfc"> GitHub</a>
|
||||
|
||||
<span><a href="../projects_instances-clusters-get" style="color: #fcfcfc;">« Previous</a></span>
|
||||
<span style="margin-left: 15px"><a href="../projects_instances-clusters-update" style="color: #fcfcfc">Next »</a></span>
|
||||
<span style="margin-left: 15px"><a href="../projects_instances-clusters-partial-update-cluster" style="color: #fcfcfc">Next »</a></span>
|
||||
</span>
|
||||
</div>
|
||||
</body>
|
||||
|
||||
@@ -0,0 +1,576 @@
|
||||
<!DOCTYPE html>
|
||||
<!--[if IE 8]><html class="no-js lt-ie9" lang="en" > <![endif]-->
|
||||
<!--[if gt IE 8]><!--> <html class="no-js" lang="en" > <!--<![endif]-->
|
||||
<head>
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Clusters Partial Update Cluster - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
<link href='https://fonts.googleapis.com/css?family=Lato:400,700|Roboto+Slab:400,700|Inconsolata:400,700' rel='stylesheet' type='text/css'>
|
||||
|
||||
<link rel="stylesheet" href="../css/theme.css" type="text/css" />
|
||||
<link rel="stylesheet" href="../css/theme_extra.css" type="text/css" />
|
||||
<link rel="stylesheet" href="../css/highlight.css">
|
||||
|
||||
<script src="//cdnjs.cloudflare.com/ajax/libs/jquery/2.1.1/jquery.min.js"></script>
|
||||
<script src="//cdnjs.cloudflare.com/ajax/libs/modernizr/2.8.3/modernizr.min.js"></script>
|
||||
<script type="text/javascript" src="../js/highlight.pack.js"></script>
|
||||
<script src="../js/theme.js"></script>
|
||||
|
||||
<style>
|
||||
body {font-size: 90%;}
|
||||
pre, code {font-size: 100%;}
|
||||
h3, h4, h5, h6 {color: #2980b9; font-weight: 300}
|
||||
</style>
|
||||
</head>
|
||||
|
||||
<body class="wy-body-for-nav" role="document">
|
||||
|
||||
<div class="wy-grid-for-nav">
|
||||
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
<div class="wy-menu wy-menu-vertical" data-spy="affix" role="navigation" aria-label="main navigation">
|
||||
<ul class="current">
|
||||
|
||||
|
||||
<span>Operations</span>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../operations_cancel">Cancel</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../operations_delete">Delete</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../operations_get">Get</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../operations_projects-operations-list">Projects Operations List</a>
|
||||
|
||||
</li>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<span>Projects</span>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-app-profiles-create">Instances App Profiles Create</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-app-profiles-delete">Instances App Profiles Delete</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-app-profiles-get">Instances App Profiles Get</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-app-profiles-list">Instances App Profiles List</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-app-profiles-patch">Instances App Profiles Patch</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-backups-create">Instances Clusters Backups Create</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-backups-delete">Instances Clusters Backups Delete</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-backups-get">Instances Clusters Backups Get</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-backups-get-iam-policy">Instances Clusters Backups Get Iam Policy</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-backups-list">Instances Clusters Backups List</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-backups-patch">Instances Clusters Backups Patch</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-backups-set-iam-policy">Instances Clusters Backups Set Iam Policy</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-backups-test-iam-permissions">Instances Clusters Backups Test Iam Permissions</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-create">Instances Clusters Create</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-delete">Instances Clusters Delete</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-get">Instances Clusters Get</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-list">Instances Clusters List</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 current">
|
||||
<a class="current" href=".">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
<ul>
|
||||
|
||||
<li class="toctree-l2"><a href="#scopes">Scopes</a></li>
|
||||
|
||||
|
||||
<li class="toctree-l2"><a href="#required-scalar-argument">Required Scalar Argument</a></li>
|
||||
|
||||
|
||||
<li class="toctree-l2"><a href="#required-request-value">Required Request Value</a></li>
|
||||
|
||||
<li><a class="toctree-l3" href="#about-cursors">About Cursors</a></li>
|
||||
|
||||
|
||||
<li class="toctree-l2"><a href="#optional-output-flags">Optional Output Flags</a></li>
|
||||
|
||||
|
||||
<li class="toctree-l2"><a href="#optional-method-properties">Optional Method Properties</a></li>
|
||||
|
||||
|
||||
<li class="toctree-l2"><a href="#optional-general-properties">Optional General Properties</a></li>
|
||||
|
||||
|
||||
</ul>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-create">Instances Create</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-delete">Instances Delete</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-get">Instances Get</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-get-iam-policy">Instances Get Iam Policy</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-list">Instances List</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-partial-update-instance">Instances Partial Update Instance</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-set-iam-policy">Instances Set Iam Policy</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-tables-check-consistency">Instances Tables Check Consistency</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-tables-create">Instances Tables Create</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-tables-delete">Instances Tables Delete</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-tables-drop-row-range">Instances Tables Drop Row Range</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-tables-generate-consistency-token">Instances Tables Generate Consistency Token</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-tables-get">Instances Tables Get</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-tables-get-iam-policy">Instances Tables Get Iam Policy</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-tables-list">Instances Tables List</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-tables-modify-column-families">Instances Tables Modify Column Families</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-tables-restore">Instances Tables Restore</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-tables-set-iam-policy">Instances Tables Set Iam Policy</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-tables-test-iam-permissions">Instances Tables Test Iam Permissions</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-test-iam-permissions">Instances Test Iam Permissions</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-update">Instances Update</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_locations-get">Locations Get</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_locations-list">Locations List</a>
|
||||
|
||||
</li>
|
||||
|
||||
|
||||
|
||||
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
|
||||
</nav>
|
||||
|
||||
<section data-toggle="wy-nav-shift" class="wy-nav-content-wrap">
|
||||
|
||||
|
||||
<nav class="wy-nav-top" role="navigation" aria-label="top navigation">
|
||||
<i data-toggle="wy-nav-top" class="icon icon-reorder"></i>
|
||||
<a href=".."></a>
|
||||
</nav>
|
||||
|
||||
|
||||
<div class="wy-nav-content">
|
||||
<div class="rst-content">
|
||||
<div role="navigation" aria-label="breadcrumbs navigation">
|
||||
<ul class="wy-breadcrumbs">
|
||||
<li><a href="..">Docs</a> »</li>
|
||||
<li>Instances Clusters Partial Update Cluster</li>
|
||||
<li class="wy-breadcrumbs-aside">
|
||||
|
||||
|
||||
<a href="https://github.com/Byron/google-apis-rs/tree/main/gen/bigtableadmin2-cli" class="icon icon-github"> Edit on GitHub</a>
|
||||
|
||||
|
||||
</li>
|
||||
</ul>
|
||||
<hr/>
|
||||
</div>
|
||||
<div role="main">
|
||||
<div class="section">
|
||||
<p>Partially updates a cluster within a project. This method is the preferred way to update a Cluster. To enable and update autoscaling, set cluster_config.cluster_autoscaling_config. When autoscaling is enabled, serve_nodes is treated as an OUTPUT_ONLY field, meaning that updates to it are ignored. Note that an update cannot simultaneously set serve_nodes to non-zero and cluster_config.cluster_autoscaling_config to non-empty, and also specify both in the update_mask. To disable autoscaling, clear cluster_config.cluster_autoscaling_config, and explicitly set a serve_node count via the update_mask.</p>
|
||||
<h1 id="scopes">Scopes</h1>
|
||||
<p>You will need authorization for at least one of the following scopes to make a valid call:</p>
|
||||
<ul>
|
||||
<li><em>https://www.googleapis.com/auth/bigtable.admin</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/bigtable.admin.cluster</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/bigtable.admin.instance</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-bigtable.admin</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-bigtable.admin.cluster</em></li>
|
||||
<li><em>https://www.googleapis.com/auth/cloud-platform</em></li>
|
||||
</ul>
|
||||
<p>If unset, the scope for this method defaults to <em>https://www.googleapis.com/auth/bigtable.admin</em>.
|
||||
You can set the scope for this method like this: <code>bigtableadmin2 --scope <scope> projects instances-clusters-partial-update-cluster ...</code></p>
|
||||
<h1 id="required-scalar-argument">Required Scalar Argument</h1>
|
||||
<ul>
|
||||
<li><strong><name></strong> <em>(string)</em><ul>
|
||||
<li>The unique name of the cluster. Values are of the form <code>projects/{project}/instances/{instance}/clusters/a-z*</code>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
<h1 id="required-request-value">Required Request Value</h1>
|
||||
<p>The request value is a data-structure with various fields. Each field may be a simple scalar or another data-structure.
|
||||
In the latter case it is advised to set the field-cursor to the data-structure's field to specify values more concisely.</p>
|
||||
<p>For example, a structure like this:</p>
|
||||
<pre><code>Cluster:
|
||||
cluster-config:
|
||||
cluster-autoscaling-config:
|
||||
autoscaling-limits:
|
||||
max-serve-nodes: integer
|
||||
min-serve-nodes: integer
|
||||
autoscaling-targets:
|
||||
cpu-utilization-percent: integer
|
||||
default-storage-type: string
|
||||
encryption-config:
|
||||
kms-key-name: string
|
||||
location: string
|
||||
name: string
|
||||
serve-nodes: integer
|
||||
state: string
|
||||
|
||||
</code></pre>
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r .cluster-config.cluster-autoscaling-config.autoscaling-limits max-serve-nodes=81</code><ul>
|
||||
<li>Required. Maximum number of nodes to scale up to.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>min-serve-nodes=67</code></p>
|
||||
<ul>
|
||||
<li>Required. Minimum number of nodes to scale down to.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..autoscaling-targets cpu-utilization-percent=79</code></p>
|
||||
<ul>
|
||||
<li>The cpu utilization that the Autoscaler should be trying to achieve. This number is on a scale from 0 (no utilization) to 100 (total utilization), and is limited between 10 and 80.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.... default-storage-type=voluptua.</code></p>
|
||||
<ul>
|
||||
<li>Immutable. The type of storage used by this cluster to serve its parent instance's tables, unless explicitly overridden.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>encryption-config kms-key-name=amet.</code></p>
|
||||
<ul>
|
||||
<li>Describes the Cloud KMS encryption key that will be used to protect the destination Bigtable cluster. The requirements for this key are: 1) The Cloud Bigtable service account associated with the project that contains this cluster must be granted the <code>cloudkms.cryptoKeyEncrypterDecrypter</code> role on the CMEK key. 2) Only regional keys can be used and the region of the CMEK key must match the region of the cluster. 3) All clusters within an instance must use the same CMEK key. Values are of the form <code>projects/{project}/locations/{location}/keyRings/{keyring}/cryptoKeys/{key}</code></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. location=consetetur</code></p>
|
||||
<ul>
|
||||
<li>Immutable. The location where this cluster's nodes and storage reside. For best performance, clients should be located as close as possible to this cluster. Currently only zones are supported, so values should be of the form <code>projects/{project}/locations/{zone}</code>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>name=diam</code><ul>
|
||||
<li>The unique name of the cluster. Values are of the form <code>projects/{project}/instances/{instance}/clusters/a-z*</code>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>serve-nodes=52</code><ul>
|
||||
<li>The number of nodes allocated to this cluster. More nodes enable higher throughput and more consistent performance.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>state=et</code><ul>
|
||||
<li>Output only. The current state of the cluster.</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
<h3 id="about-cursors">About Cursors</h3>
|
||||
<p>The cursor position is key to comfortably set complex nested structures. The following rules apply:</p>
|
||||
<ul>
|
||||
<li>The cursor position is always set relative to the current one, unless the field name starts with the <code>.</code> character. Fields can be nested such as in <code>-r f.s.o</code> .</li>
|
||||
<li>The cursor position is set relative to the top-level structure if it starts with <code>.</code>, e.g. <code>-r .s.s</code></li>
|
||||
<li>You can also set nested fields without setting the cursor explicitly. For example, to set a value relative to the current cursor position, you would specify <code>-r struct.sub_struct=bar</code>.</li>
|
||||
<li>You can move the cursor one level up by using <code>..</code>. Each additional <code>.</code> moves it up one additional level. E.g. <code>...</code> would go three levels up.</li>
|
||||
</ul>
|
||||
<h1 id="optional-output-flags">Optional Output Flags</h1>
|
||||
<p>The method's return value a JSON encoded structure, which will be written to standard output by default.</p>
|
||||
<ul>
|
||||
<li><strong>-o out</strong><ul>
|
||||
<li><em>out</em> specifies the <em>destination</em> to which to write the server's result to.
|
||||
It will be a JSON-encoded structure.
|
||||
The <em>destination</em> may be <code>-</code> to indicate standard output, or a filepath that is to contain the received bytes.
|
||||
If unset, it defaults to standard output.</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
<h1 id="optional-method-properties">Optional Method Properties</h1>
|
||||
<p>You may set the following properties to further configure the call. Please note that <code>-p</code> is followed by one
|
||||
or more key-value-pairs, and is called like this <code>-p k1=v1 k2=v2</code> even though the listing below repeats the
|
||||
<code>-p</code> for completeness.</p>
|
||||
<ul>
|
||||
<li><strong>-p update-mask=string</strong><ul>
|
||||
<li>Required. The subset of Cluster fields which should be replaced.</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
<h1 id="optional-general-properties">Optional General Properties</h1>
|
||||
<p>The following properties can configure any call, and are not specific to this method.</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p><strong>-p $-xgafv=string</strong></p>
|
||||
<ul>
|
||||
<li>V1 error format.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>-p access-token=string</strong></p>
|
||||
<ul>
|
||||
<li>OAuth access token.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>-p alt=string</strong></p>
|
||||
<ul>
|
||||
<li>Data format for response.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>-p callback=string</strong></p>
|
||||
<ul>
|
||||
<li>JSONP</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>-p fields=string</strong></p>
|
||||
<ul>
|
||||
<li>Selector specifying which fields to include in a partial response.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>-p key=string</strong></p>
|
||||
<ul>
|
||||
<li>API key. Your API key identifies your project and provides you with API access, quota, and reports. Required unless you provide an OAuth 2.0 token.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>-p oauth-token=string</strong></p>
|
||||
<ul>
|
||||
<li>OAuth 2.0 token for the current user.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>-p pretty-print=boolean</strong></p>
|
||||
<ul>
|
||||
<li>Returns response with indentations and line breaks.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>-p quota-user=string</strong></p>
|
||||
<ul>
|
||||
<li>Available to use for quota purposes for server-side applications. Can be any arbitrary string assigned to a user, but should not exceed 40 characters.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>-p upload-type=string</strong></p>
|
||||
<ul>
|
||||
<li>Legacy upload protocol for media (e.g. "media", "multipart").</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>-p upload-protocol=string</strong></p>
|
||||
<ul>
|
||||
<li>Upload protocol for media (e.g. "raw", "multipart").</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
<footer>
|
||||
|
||||
<div class="rst-footer-buttons" role="navigation" aria-label="footer navigation">
|
||||
|
||||
<a href="../projects_instances-clusters-update" class="btn btn-neutral float-right" title="Instances Clusters Update"/>Next <span class="icon icon-circle-arrow-right"></span></a>
|
||||
|
||||
|
||||
<a href="../projects_instances-clusters-list" class="btn btn-neutral" title="Instances Clusters List"><span class="icon icon-circle-arrow-left"></span> Previous</a>
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
<hr/>
|
||||
|
||||
<div role="contentinfo">
|
||||
<p>
|
||||
<!-- Copyright etc -->
|
||||
</p>
|
||||
</div>
|
||||
|
||||
Built with <a href="http://www.mkdocs.org">MkDocs</a>, using a <a href="https://github.com/snide/sphinx_rtd_theme">theme</a> provided by <a href="https://readthedocs.org">Read the Docs</a>.
|
||||
</footer>
|
||||
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</section>
|
||||
|
||||
</div>
|
||||
|
||||
<div class="rst-versions" role="note" style="cursor: pointer">
|
||||
<span class="rst-current-version" data-toggle="rst-current-version">
|
||||
|
||||
<a class="icon icon-github" style="float: left; color: #fcfcfc"> GitHub</a>
|
||||
|
||||
<span><a href="../projects_instances-clusters-list" style="color: #fcfcfc;">« Previous</a></span>
|
||||
<span style="margin-left: 15px"><a href="../projects_instances-clusters-update" style="color: #fcfcfc">Next »</a></span>
|
||||
</span>
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Clusters Update - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances Clusters Update - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -155,6 +155,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 current">
|
||||
<a class="current" href=".">Instances Clusters Update</a>
|
||||
|
||||
@@ -332,7 +337,7 @@
|
||||
</div>
|
||||
<div role="main">
|
||||
<div class="section">
|
||||
<p>Updates a cluster within an instance.</p>
|
||||
<p>Updates a cluster within an instance. Note that UpdateCluster does not support updating cluster_config.cluster_autoscaling_config. In order to update it, you must use PartialUpdateCluster.</p>
|
||||
<h1 id="scopes">Scopes</h1>
|
||||
<p>You will need authorization for at least one of the following scopes to make a valid call:</p>
|
||||
<ul>
|
||||
@@ -357,6 +362,13 @@ You can set the scope for this method like this: <code>bigtableadmin2 --scope &l
|
||||
In the latter case it is advised to set the field-cursor to the data-structure's field to specify values more concisely.</p>
|
||||
<p>For example, a structure like this:</p>
|
||||
<pre><code>Cluster:
|
||||
cluster-config:
|
||||
cluster-autoscaling-config:
|
||||
autoscaling-limits:
|
||||
max-serve-nodes: integer
|
||||
min-serve-nodes: integer
|
||||
autoscaling-targets:
|
||||
cpu-utilization-percent: integer
|
||||
default-storage-type: string
|
||||
encryption-config:
|
||||
kms-key-name: string
|
||||
@@ -369,31 +381,49 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r . default-storage-type=et</code><ul>
|
||||
<li><code>-r .cluster-config.cluster-autoscaling-config.autoscaling-limits max-serve-nodes=79</code><ul>
|
||||
<li>Required. Maximum number of nodes to scale up to.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>min-serve-nodes=6</code></p>
|
||||
<ul>
|
||||
<li>Required. Minimum number of nodes to scale down to.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>..autoscaling-targets cpu-utilization-percent=86</code></p>
|
||||
<ul>
|
||||
<li>The cpu utilization that the Autoscaler should be trying to achieve. This number is on a scale from 0 (no utilization) to 100 (total utilization), and is limited between 10 and 80.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.... default-storage-type=dolor</code></p>
|
||||
<ul>
|
||||
<li>Immutable. The type of storage used by this cluster to serve its parent instance's tables, unless explicitly overridden.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>encryption-config kms-key-name=sed</code></p>
|
||||
<p><code>encryption-config kms-key-name=duo</code></p>
|
||||
<ul>
|
||||
<li>Describes the Cloud KMS encryption key that will be used to protect the destination Bigtable cluster. The requirements for this key are: 1) The Cloud Bigtable service account associated with the project that contains this cluster must be granted the <code>cloudkms.cryptoKeyEncrypterDecrypter</code> role on the CMEK key. 2) Only regional keys can be used and the region of the CMEK key must match the region of the cluster. 3) All clusters within an instance must use the same CMEK key. Values are of the form <code>projects/{project}/locations/{location}/keyRings/{keyring}/cryptoKeys/{key}</code></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. location=et</code></p>
|
||||
<p><code>.. location=vero</code></p>
|
||||
<ul>
|
||||
<li>Immutable. The location where this cluster's nodes and storage reside. For best performance, clients should be located as close as possible to this cluster. Currently only zones are supported, so values should be of the form <code>projects/{project}/locations/{zone}</code>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>name=et</code><ul>
|
||||
<li><code>name=vero</code><ul>
|
||||
<li>The unique name of the cluster. Values are of the form <code>projects/{project}/instances/{instance}/clusters/a-z*</code>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>serve-nodes=25</code><ul>
|
||||
<li>Required. The number of nodes allocated to this cluster. More nodes enable higher throughput and more consistent performance.</li>
|
||||
<li><code>serve-nodes=13</code><ul>
|
||||
<li>The number of nodes allocated to this cluster. More nodes enable higher throughput and more consistent performance.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>state=erat</code><ul>
|
||||
<li><code>state=stet</code><ul>
|
||||
<li>Output only. The current state of the cluster.</li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -497,7 +527,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<a href="../projects_instances-create" class="btn btn-neutral float-right" title="Instances Create"/>Next <span class="icon icon-circle-arrow-right"></span></a>
|
||||
|
||||
|
||||
<a href="../projects_instances-clusters-list" class="btn btn-neutral" title="Instances Clusters List"><span class="icon icon-circle-arrow-left"></span> Previous</a>
|
||||
<a href="../projects_instances-clusters-partial-update-cluster" class="btn btn-neutral" title="Instances Clusters Partial Update Cluster"><span class="icon icon-circle-arrow-left"></span> Previous</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -525,7 +555,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<a class="icon icon-github" style="float: left; color: #fcfcfc"> GitHub</a>
|
||||
|
||||
<span><a href="../projects_instances-clusters-list" style="color: #fcfcfc;">« Previous</a></span>
|
||||
<span><a href="../projects_instances-clusters-partial-update-cluster" style="color: #fcfcfc;">« Previous</a></span>
|
||||
<span style="margin-left: 15px"><a href="../projects_instances-create" style="color: #fcfcfc">Next »</a></span>
|
||||
</span>
|
||||
</div>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Create - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances Create - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -155,6 +155,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
@@ -332,7 +337,7 @@
|
||||
</div>
|
||||
<div role="main">
|
||||
<div class="section">
|
||||
<p>Create an instance within a project.</p>
|
||||
<p>Create an instance within a project. Note that exactly one of Cluster.serve_nodes and Cluster.cluster_config.cluster_autoscaling_config can be set. If serve_nodes is set to non-zero, then the cluster is manually scaled. If cluster_config.cluster_autoscaling_config is non-empty, then autoscaling is enabled.</p>
|
||||
<h1 id="scopes">Scopes</h1>
|
||||
<p>You will need authorization for at least one of the following scopes to make a valid call:</p>
|
||||
<ul>
|
||||
@@ -358,6 +363,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<p>For example, a structure like this:</p>
|
||||
<pre><code>CreateInstanceRequest:
|
||||
instance:
|
||||
create-time: string
|
||||
display-name: string
|
||||
labels: { string: string }
|
||||
name: string
|
||||
@@ -370,36 +376,40 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r .instance display-name=sed</code><ul>
|
||||
<li><code>-r .instance create-time=vero</code><ul>
|
||||
<li>Output only. A server-assigned timestamp representing when this Instance was created. For instances created before this field was added (August 2021), this value is <code>seconds: 0, nanos: 1</code>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>display-name=elitr</code><ul>
|
||||
<li>Required. The descriptive name for this instance as it appears in UIs. Can be changed at any time, but should be kept globally unique to avoid confusion.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>labels=key=duo</code><ul>
|
||||
<li><code>labels=key=lorem</code><ul>
|
||||
<li>Required. Labels are a flexible and lightweight mechanism for organizing cloud resources into groups that reflect a customer's organizational needs and deployment strategies. They can be used to filter resources and aggregate metrics. * Label keys must be between 1 and 63 characters long and must conform to the regular expression: <code>\p{Ll}\p{Lo}{0,62}</code>. * Label values must be between 0 and 63 characters long and must conform to the regular expression: <code>[\p{Ll}\p{Lo}\p{N}_-]{0,63}</code>. * No more than 64 labels can be associated with a given resource. * Keys and values must both be under 128 bytes.</li>
|
||||
<li>the value will be associated with the given <code>key</code></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>name=dolore</code><ul>
|
||||
<li><code>name=diam</code><ul>
|
||||
<li>The unique name of the instance. Values are of the form <code>projects/{project}/instances/a-z+[a-z0-9]</code>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>state=et</code><ul>
|
||||
<li><code>state=no</code><ul>
|
||||
<li>Output only. The current state of the instance.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>type=voluptua.</code></p>
|
||||
<p><code>type=ipsum</code></p>
|
||||
<ul>
|
||||
<li>Required. The type of the instance. Defaults to <code>PRODUCTION</code>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. instance-id=amet.</code></p>
|
||||
<p><code>.. instance-id=accusam</code></p>
|
||||
<ul>
|
||||
<li>Required. The ID to be used when referring to the new instance within its project, e.g., just <code>myinstance</code> rather than <code>projects/myproject/instances/myinstance</code>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>parent=consetetur</code><ul>
|
||||
<li><code>parent=takimata</code><ul>
|
||||
<li>Required. The unique name of the project in which to create the new instance. Values are of the form <code>projects/{project}</code>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Delete - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances Delete - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -155,6 +155,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Get Iam Policy - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances Get Iam Policy - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -155,6 +155,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
@@ -364,8 +369,8 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r .options requested-policy-version=9</code><ul>
|
||||
<li>Optional. The policy format version to be returned. Valid values are 0, 1, and 3. Requests specifying an invalid value will be rejected. Requests for policies with any conditional bindings must specify version 3. Policies without any conditional bindings may specify any valid value or leave the field unset. To learn which resources support conditions in their IAM policies, see the <a href="https://cloud.google.com/iam/help/conditions/resource-policies">IAM documentation</a>.</li>
|
||||
<li><code>-r .options requested-policy-version=55</code><ul>
|
||||
<li>Optional. The maximum policy version that will be used to format the policy. Valid values are 0, 1, and 3. Requests specifying an invalid value will be rejected. Requests for policies with any conditional role bindings must specify version 3. Policies with no conditional role bindings may specify any valid value or leave the field unset. The policy in the response might use the policy version that you specified, or it might use a lower policy version. For example, if you specify version 3, but the policy has no conditional role bindings, the response uses version 1. To learn which resources support conditions in their IAM policies, see the <a href="https://cloud.google.com/iam/help/conditions/resource-policies">IAM documentation</a>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Get - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances Get - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -155,6 +155,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances List - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances List - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -155,6 +155,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Partial Update Instance - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances Partial Update Instance - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -155,6 +155,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
@@ -360,6 +365,7 @@ You can set the scope for this method like this: <code>bigtableadmin2 --scope &l
|
||||
In the latter case it is advised to set the field-cursor to the data-structure's field to specify values more concisely.</p>
|
||||
<p>For example, a structure like this:</p>
|
||||
<pre><code>Instance:
|
||||
create-time: string
|
||||
display-name: string
|
||||
labels: { string: string }
|
||||
name: string
|
||||
@@ -370,24 +376,28 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r . display-name=dolor</code><ul>
|
||||
<li><code>-r . create-time=voluptua.</code><ul>
|
||||
<li>Output only. A server-assigned timestamp representing when this Instance was created. For instances created before this field was added (August 2021), this value is <code>seconds: 0, nanos: 1</code>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>display-name=et</code><ul>
|
||||
<li>Required. The descriptive name for this instance as it appears in UIs. Can be changed at any time, but should be kept globally unique to avoid confusion.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>labels=key=et</code><ul>
|
||||
<li><code>labels=key=erat</code><ul>
|
||||
<li>Required. Labels are a flexible and lightweight mechanism for organizing cloud resources into groups that reflect a customer's organizational needs and deployment strategies. They can be used to filter resources and aggregate metrics. * Label keys must be between 1 and 63 characters long and must conform to the regular expression: <code>\p{Ll}\p{Lo}{0,62}</code>. * Label values must be between 0 and 63 characters long and must conform to the regular expression: <code>[\p{Ll}\p{Lo}\p{N}_-]{0,63}</code>. * No more than 64 labels can be associated with a given resource. * Keys and values must both be under 128 bytes.</li>
|
||||
<li>the value will be associated with the given <code>key</code></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>name=et</code><ul>
|
||||
<li><code>name=consetetur</code><ul>
|
||||
<li>The unique name of the instance. Values are of the form <code>projects/{project}/instances/a-z+[a-z0-9]</code>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>state=sadipscing</code><ul>
|
||||
<li><code>state=amet.</code><ul>
|
||||
<li>Output only. The current state of the instance.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>type=stet</code><ul>
|
||||
<li><code>type=sed</code><ul>
|
||||
<li>Required. The type of the instance. Defaults to <code>PRODUCTION</code>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Set Iam Policy - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances Set Iam Policy - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -155,6 +155,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
@@ -366,18 +371,18 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r .policy etag=dolor</code><ul>
|
||||
<li><code>-r .policy etag=takimata</code><ul>
|
||||
<li><code>etag</code> is used for optimistic concurrency control as a way to help prevent simultaneous updates of a policy from overwriting each other. It is strongly suggested that systems make use of the <code>etag</code> in the read-modify-write cycle to perform policy updates in order to avoid race conditions: An <code>etag</code> is returned in the response to <code>getIamPolicy</code>, and systems are expected to put that etag in the request to <code>setIamPolicy</code> to ensure that their change will be applied to the same version of the policy. <strong>Important:</strong> If you use IAM Conditions, you must include the <code>etag</code> field whenever you call <code>setIamPolicy</code>. If you omit this field, then IAM allows you to overwrite a version <code>3</code> policy with a version <code>1</code> policy, and all of the conditions in the version <code>3</code> policy are lost.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>version=81</code></p>
|
||||
<p><code>version=82</code></p>
|
||||
<ul>
|
||||
<li>Specifies the format of the policy. Valid values are <code>0</code>, <code>1</code>, and <code>3</code>. Requests that specify an invalid value are rejected. Any operation that affects conditional role bindings must specify version <code>3</code>. This requirement applies to the following operations: * Getting a policy that includes a conditional role binding * Adding a conditional role binding to a policy * Changing a conditional role binding in a policy * Removing any role binding, with or without a condition, from a policy that includes conditions <strong>Important:</strong> If you use IAM Conditions, you must include the <code>etag</code> field whenever you call <code>setIamPolicy</code>. If you omit this field, then IAM allows you to overwrite a version <code>3</code> policy with a version <code>1</code> policy, and all of the conditions in the version <code>3</code> policy are lost. If a policy does not include any conditions, operations on that policy may specify any valid version or leave the field unset. To learn which resources support conditions in their IAM policies, see the <a href="https://cloud.google.com/iam/help/conditions/resource-policies">IAM documentation</a>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. update-mask=vero</code></p>
|
||||
<p><code>.. update-mask=gubergren</code></p>
|
||||
<ul>
|
||||
<li>OPTIONAL: A FieldMask specifying which fields of the policy to modify. Only the fields in the mask will be modified. If no mask is provided, the following default mask is used: <code>paths: &#34;bindings, etag&#34;</code></li>
|
||||
</ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Tables Check Consistency - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances Tables Check Consistency - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -155,6 +155,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
@@ -362,7 +367,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r . consistency-token=vero</code><ul>
|
||||
<li><code>-r . consistency-token=et</code><ul>
|
||||
<li>Required. The token created using GenerateConsistencyToken for the Table.</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Tables Create - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances Tables Create - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -155,6 +155,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
@@ -372,40 +377,40 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r .table granularity=invidunt</code><ul>
|
||||
<li><code>-r .table granularity=accusam</code><ul>
|
||||
<li>Immutable. The granularity (i.e. <code>MILLIS</code>) at which timestamps are stored in this table. Timestamps not matching the granularity will be rejected. If unspecified at creation time, the value will be set to <code>MILLIS</code>. Views: <code>SCHEMA_VIEW</code>, <code>FULL</code>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>name=stet</code><ul>
|
||||
<li><code>name=voluptua.</code><ul>
|
||||
<li>The unique name of the table. Values are of the form <code>projects/{project}/instances/{instance}/tables/_a-zA-Z0-9*</code>. Views: <code>NAME_ONLY</code>, <code>SCHEMA_VIEW</code>, <code>REPLICATION_VIEW</code>, <code>FULL</code></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>restore-info.backup-info backup=vero</code><ul>
|
||||
<li><code>restore-info.backup-info backup=dolore</code><ul>
|
||||
<li>Output only. Name of the backup.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>end-time=elitr</code><ul>
|
||||
<li><code>end-time=dolore</code><ul>
|
||||
<li>Output only. This time that the backup was finished. Row data in the backup will be no newer than this timestamp.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>source-table=lorem</code><ul>
|
||||
<li><code>source-table=dolore</code><ul>
|
||||
<li>Output only. Name of the table the backup was created from.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>start-time=diam</code></p>
|
||||
<p><code>start-time=voluptua.</code></p>
|
||||
<ul>
|
||||
<li>Output only. The time that the backup was started. Row data in the backup will be no older than this timestamp.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. source-type=no</code></p>
|
||||
<p><code>.. source-type=amet.</code></p>
|
||||
<ul>
|
||||
<li>The type of the restore source.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>... table-id=ipsum</code></p>
|
||||
<p><code>... table-id=ea</code></p>
|
||||
<ul>
|
||||
<li>Required. The name by which the new table should be referred to within the parent instance, e.g., <code>foobar</code> rather than <code>{parent}/tables/foobar</code>. Maximum 50 characters.</li>
|
||||
</ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Tables Delete - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances Tables Delete - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -155,6 +155,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Tables Drop Row Range - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances Tables Drop Row Range - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -155,6 +155,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
@@ -363,11 +368,11 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r . delete-all-data-from-table=true</code><ul>
|
||||
<li><code>-r . delete-all-data-from-table=false</code><ul>
|
||||
<li>Delete all rows in the table. Setting this to false is a no-op.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>row-key-prefix=consetetur</code><ul>
|
||||
<li><code>row-key-prefix=lorem</code><ul>
|
||||
<li>Delete all rows that start with this row key prefix. Prefix cannot be zero length.</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Tables Generate Consistency Token - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances Tables Generate Consistency Token - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -155,6 +155,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Tables Get Iam Policy - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances Tables Get Iam Policy - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -155,6 +155,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
@@ -363,8 +368,8 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r .options requested-policy-version=73</code><ul>
|
||||
<li>Optional. The policy format version to be returned. Valid values are 0, 1, and 3. Requests specifying an invalid value will be rejected. Requests for policies with any conditional bindings must specify version 3. Policies without any conditional bindings may specify any valid value or leave the field unset. To learn which resources support conditions in their IAM policies, see the <a href="https://cloud.google.com/iam/help/conditions/resource-policies">IAM documentation</a>.</li>
|
||||
<li><code>-r .options requested-policy-version=63</code><ul>
|
||||
<li>Optional. The maximum policy version that will be used to format the policy. Valid values are 0, 1, and 3. Requests specifying an invalid value will be rejected. Requests for policies with any conditional role bindings must specify version 3. Policies with no conditional role bindings may specify any valid value or leave the field unset. The policy in the response might use the policy version that you specified, or it might use a lower policy version. For example, if you specify version 3, but the policy has no conditional role bindings, the response uses version 1. To learn which resources support conditions in their IAM policies, see the <a href="https://cloud.google.com/iam/help/conditions/resource-policies">IAM documentation</a>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Tables Get - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances Tables Get - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -155,6 +155,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Tables List - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances Tables List - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -155,6 +155,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
@@ -381,7 +386,7 @@ or more key-value-pairs, and is called like this <code>-p k1=v1 k2=v2</code> eve
|
||||
<li>
|
||||
<p><strong>-p view=string</strong></p>
|
||||
<ul>
|
||||
<li>The view to be applied to the returned tables' fields. Only NAME_ONLY view (default) and REPLICATION_VIEW are supported.</li>
|
||||
<li>The view to be applied to the returned tables' fields. Only NAME_ONLY view (default), REPLICATION_VIEW and ENCRYPTION_VIEW are supported.</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Tables Modify Column Families - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances Tables Modify Column Families - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -155,6 +155,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Tables Restore - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances Tables Restore - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -155,6 +155,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
@@ -332,7 +337,7 @@
|
||||
</div>
|
||||
<div role="main">
|
||||
<div class="section">
|
||||
<p>Create a new table by restoring from a completed backup. The new table must be in the same instance as the instance containing the backup. The returned table long-running operation can be used to track the progress of the operation, and to cancel it. The metadata field type is RestoreTableMetadata. The response type is Table, if successful.</p>
|
||||
<p>Create a new table by restoring from a completed backup. The new table must be in the same project as the instance containing the backup. The returned table long-running operation can be used to track the progress of the operation, and to cancel it. The metadata field type is RestoreTableMetadata. The response type is Table, if successful.</p>
|
||||
<h1 id="scopes">Scopes</h1>
|
||||
<p>You will need authorization for at least one of the following scopes to make a valid call:</p>
|
||||
<ul>
|
||||
@@ -347,7 +352,7 @@ You can set the scope for this method like this: <code>bigtableadmin2 --scope &l
|
||||
<h1 id="required-scalar-argument">Required Scalar Argument</h1>
|
||||
<ul>
|
||||
<li><strong><parent></strong> <em>(string)</em><ul>
|
||||
<li>Required. The name of the instance in which to create the restored table. This instance must be the parent of the source backup. Values are of the form <code>projects//instances/</code>.</li>
|
||||
<li>Required. The name of the instance in which to create the restored table. This instance must be in the same project as the source backup. Values are of the form <code>projects//instances/</code>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
@@ -363,11 +368,11 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r . backup=et</code><ul>
|
||||
<li><code>-r . backup=no</code><ul>
|
||||
<li>Name of the backup from which to restore. Values are of the form <code>projects//instances//clusters//backups/</code>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>table-id=erat</code><ul>
|
||||
<li><code>table-id=est</code><ul>
|
||||
<li>Required. The id of the table to create and restore to. This table must not already exist. The <code>table_id</code> appended to <code>parent</code> forms the full table name of the form <code>projects//instances//tables/</code>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Tables Set Iam Policy - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances Tables Set Iam Policy - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -155,6 +155,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
@@ -365,18 +370,18 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r .policy etag=consetetur</code><ul>
|
||||
<li><code>-r .policy etag=at</code><ul>
|
||||
<li><code>etag</code> is used for optimistic concurrency control as a way to help prevent simultaneous updates of a policy from overwriting each other. It is strongly suggested that systems make use of the <code>etag</code> in the read-modify-write cycle to perform policy updates in order to avoid race conditions: An <code>etag</code> is returned in the response to <code>getIamPolicy</code>, and systems are expected to put that etag in the request to <code>setIamPolicy</code> to ensure that their change will be applied to the same version of the policy. <strong>Important:</strong> If you use IAM Conditions, you must include the <code>etag</code> field whenever you call <code>setIamPolicy</code>. If you omit this field, then IAM allows you to overwrite a version <code>3</code> policy with a version <code>1</code> policy, and all of the conditions in the version <code>3</code> policy are lost.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>version=99</code></p>
|
||||
<p><code>version=58</code></p>
|
||||
<ul>
|
||||
<li>Specifies the format of the policy. Valid values are <code>0</code>, <code>1</code>, and <code>3</code>. Requests that specify an invalid value are rejected. Any operation that affects conditional role bindings must specify version <code>3</code>. This requirement applies to the following operations: * Getting a policy that includes a conditional role binding * Adding a conditional role binding to a policy * Changing a conditional role binding in a policy * Removing any role binding, with or without a condition, from a policy that includes conditions <strong>Important:</strong> If you use IAM Conditions, you must include the <code>etag</code> field whenever you call <code>setIamPolicy</code>. If you omit this field, then IAM allows you to overwrite a version <code>3</code> policy with a version <code>1</code> policy, and all of the conditions in the version <code>3</code> policy are lost. If a policy does not include any conditions, operations on that policy may specify any valid version or leave the field unset. To learn which resources support conditions in their IAM policies, see the <a href="https://cloud.google.com/iam/help/conditions/resource-policies">IAM documentation</a>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>.. update-mask=sed</code></p>
|
||||
<p><code>.. update-mask=sit</code></p>
|
||||
<ul>
|
||||
<li>OPTIONAL: A FieldMask specifying which fields of the policy to modify. Only the fields in the mask will be modified. If no mask is provided, the following default mask is used: <code>paths: &#34;bindings, etag&#34;</code></li>
|
||||
</ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Tables Test Iam Permissions - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances Tables Test Iam Permissions - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -155,6 +155,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
@@ -362,7 +367,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r . permissions=takimata</code><ul>
|
||||
<li><code>-r . permissions=et</code><ul>
|
||||
<li>The set of permissions to check for the <code>resource</code>. Permissions with wildcards (such as '<em>' or 'storage.</em>') are not allowed. For more information see <a href="https://cloud.google.com/iam/docs/overview#permissions">IAM Overview</a>.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Test Iam Permissions - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances Test Iam Permissions - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -155,6 +155,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
@@ -363,7 +368,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r . permissions=dolores</code><ul>
|
||||
<li><code>-r . permissions=tempor</code><ul>
|
||||
<li>The set of permissions to check for the <code>resource</code>. Permissions with wildcards (such as '<em>' or 'storage.</em>') are not allowed. For more information see <a href="https://cloud.google.com/iam/docs/overview#permissions">IAM Overview</a>.</li>
|
||||
<li>Each invocation of this argument appends the given value to the array.</li>
|
||||
</ul>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Instances Update - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Instances Update - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -155,6 +155,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
@@ -357,6 +362,7 @@ You can set the scope for this method like this: <code>bigtableadmin2 --scope &l
|
||||
In the latter case it is advised to set the field-cursor to the data-structure's field to specify values more concisely.</p>
|
||||
<p>For example, a structure like this:</p>
|
||||
<pre><code>Instance:
|
||||
create-time: string
|
||||
display-name: string
|
||||
labels: { string: string }
|
||||
name: string
|
||||
@@ -367,7 +373,11 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
|
||||
<p>can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.</p>
|
||||
<ul>
|
||||
<li><code>-r . display-name=gubergren</code><ul>
|
||||
<li><code>-r . create-time=aliquyam</code><ul>
|
||||
<li>Output only. A server-assigned timestamp representing when this Instance was created. For instances created before this field was added (August 2021), this value is <code>seconds: 0, nanos: 1</code>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>display-name=ipsum</code><ul>
|
||||
<li>Required. The descriptive name for this instance as it appears in UIs. Can be changed at any time, but should be kept globally unique to avoid confusion.</li>
|
||||
</ul>
|
||||
</li>
|
||||
@@ -376,15 +386,15 @@ In the latter case it is advised to set the field-cursor to the data-structure's
|
||||
<li>the value will be associated with the given <code>key</code></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>name=accusam</code><ul>
|
||||
<li><code>name=sanctus</code><ul>
|
||||
<li>The unique name of the instance. Values are of the form <code>projects/{project}/instances/a-z+[a-z0-9]</code>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>state=voluptua.</code><ul>
|
||||
<li><code>state=lorem</code><ul>
|
||||
<li>Output only. The current state of the instance.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><code>type=dolore</code><ul>
|
||||
<li><code>type=est</code><ul>
|
||||
<li>Required. The type of the instance. Defaults to <code>PRODUCTION</code>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Locations Get - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Locations Get - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -155,6 +155,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<meta charset="utf-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
|
||||
<title>Locations List - Bigtable Admin v2.0.4+20210323</title>
|
||||
<title>Locations List - Bigtable Admin v3.0.0+20220222</title>
|
||||
|
||||
|
||||
|
||||
@@ -34,7 +34,7 @@
|
||||
|
||||
<nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
|
||||
<div class="wy-side-nav-search">
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v2.0.4+20210323</a>
|
||||
<a href=".." class="icon icon-home"> Bigtable Admin v3.0.0+20220222</a>
|
||||
|
||||
</div>
|
||||
|
||||
@@ -155,6 +155,11 @@
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-partial-update-cluster">Instances Clusters Partial Update Cluster</a>
|
||||
|
||||
</li>
|
||||
|
||||
<li class="toctree-l1 ">
|
||||
<a class="" href="../projects_instances-clusters-update">Instances Clusters Update</a>
|
||||
|
||||
@@ -370,19 +375,19 @@ or more key-value-pairs, and is called like this <code>-p k1=v1 k2=v2</code> eve
|
||||
<li>
|
||||
<p><strong>-p filter=string</strong></p>
|
||||
<ul>
|
||||
<li>The standard list filter.</li>
|
||||
<li>A filter to narrow down results to a preferred subset. The filtering language accepts strings like "displayName=tokyo", and is documented in more detail in <a href="https://google.aip.dev/160">AIP-160</a>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>-p page-size=integer</strong></p>
|
||||
<ul>
|
||||
<li>The standard list page size.</li>
|
||||
<li>The maximum number of results to return. If not set, the service selects a default.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>
|
||||
<p><strong>-p page-token=string</strong></p>
|
||||
<ul>
|
||||
<li>The standard list page token.</li>
|
||||
<li>A page token received from the <code>next_page_token</code> field in the response. Send that page token to receive the subsequent page.</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
Reference in New Issue
Block a user