gcloud: Wed Mar 27 09:52:07 UTC 2024

gcloud/alpha/bigtable/authorized-views/update

@@ -0,0 +1,132 @@
+NAME
+    gcloud alpha bigtable authorized-views update - update an existing Cloud
+        Bigtable authorized view
+
+SYNOPSIS
+    gcloud alpha bigtable authorized-views update
+        (AUTHORIZED_VIEW : --instance=INSTANCE --table=TABLE) [--async]
+        [--definition-file=DEFINITION_FILE] [--ignore-warnings]
+        [--no-interactive] [--pre-encoded] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) Update an existing Cloud Bigtable authorized view.
+
+EXAMPLES
+    To update the authorized view 'my-authorized-view' in instance
+    'my-instance' and table 'my-table', using the definition file
+    'authorized_view.json':
+
+        $ gcloud alpha bigtable authorized-views update my-authorized-view \
+            --instance=test-instance --table=test-table \
+            --definition-file=authorized_view.json
+
+    To update the authorized view 'my-authorized-view' in instance
+    'my-instance' and table 'my-table', using the pre-encoded definition file
+    'authorized_view_pre_encoded.json':
+
+        $ gcloud alpha bigtable authorized-views update my-authorized-view \
+            --instance=test-instance --table=test-table \
+            --definition-file=authorized_view_pre_encoded.json --pre-encoded
+
+    To update the authorized view 'my-authorized-view' in instance
+    'my-instance' and table 'my-table', using the definition file
+    'authorized_view.json' and skip the prompt to proceed or cancel the update:
+
+        $ gcloud alpha bigtable authorized-views update my-authorized-view \
+            --instance=test-instance --table=test-table \
+            --definition-file=authorized_view.json --no-interactive
+
+POSITIONAL ARGUMENTS
+     Authorized view resource - Cloud Bigtable authorized view to update. The
+     arguments in this group can be used to specify the attributes of this
+     resource. (NOTE) Some attributes are not given arguments in this group but
+     can be set in other ways.
+
+     To set the project attribute:
+      ◆ provide the argument authorized_view on the command line with a fully
+        specified name;
+      ◆ provide the argument --project on the command line;
+      ◆ set the property core/project.
+
+     This must be specified.
+
+       AUTHORIZED_VIEW
+          ID of the authorized-view or fully qualified identifier for the
+          authorized-view.
+
+          To set the authorized_view attribute:
+          ▸ provide the argument authorized_view on the command line.
+
+          This positional argument must be specified if any of the other
+          arguments in this group are specified.
+
+       --instance=INSTANCE
+          Name of the Cloud Bigtable instance.
+
+          To set the instance attribute:
+          ▸ provide the argument authorized_view on the command line with a
+            fully specified name;
+          ▸ provide the argument --instance on the command line.
+
+       --table=TABLE
+          Name of the Cloud Bigtable table.
+
+          To set the table attribute:
+          ▸ provide the argument authorized_view on the command line with a
+            fully specified name;
+          ▸ provide the argument --table on the command line.
+
+FLAGS
+     --async
+        Return immediately, without waiting for the operation in progress to
+        complete.
+
+     --definition-file=DEFINITION_FILE
+        Path to a JSON or YAML file containing a valid authorized view
+        protobuf.
+
+        The 'name' field is ignored. The name is deduced from the other command
+        line arguments.
+
+        Example: { "subsetView": { "rowPrefixes": ["store1"], "familySubsets":
+        { "column_family_name": { "qualifiers":["address"],
+        "qualifierPrefixes":["tel"] } } }, "deletionProtection": true }
+
+     --ignore-warnings
+        If true, changes that make the authorized view more restrictive are
+        allowed.
+
+     --interactive
+        If provided, a diff is displayed with a prompt to proceed or cancel the
+        update. Enabled by default, use --no-interactive to disable.
+
+     --pre-encoded
+        By default, Base64 encoding is applied to all binary fields
+        ("rowPrefixes", "qualifiers" and "qualifierPrefixes") in the JSON or
+        YAML definition file.
+
+        Use this to indicate that all binary fields are already Base64-encoded
+        and should be used directly.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+API REFERENCE
+    This command uses the bigtableadmin/v2 API. The full documentation for this
+    API can be found at: https://cloud.google.com/bigtable/
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist. These variants are also available:
+
+        $ gcloud bigtable authorized-views update
+
+        $ gcloud beta bigtable authorized-views update
+