gcloud beta bigtable authorized-views create - create a new Cloud Bigtable authorized view

gcloud beta bigtable authorized-views create(AUTHORIZED_VIEW :--instance=INSTANCE--table=TABLE)[--async][--definition-file=DEFINITION_FILE][--pre-encoded][GCLOUD_WIDE_FLAG …]

gcloudbetabigtableauthorized-viewscreatemy-authorized-view--instance=test-instance--table=test-table--definition-file=authorized_view.json

To create an authorized viewmy-authorized-view in instancemy-instance and tablemy-table, using the pre-encodeddefinition fileauthorized_view_pre_encoded.json:

gcloudbetabigtableauthorized-viewscreatemy-authorized-view--instance=test-instance--table=test-table--definition-file=authorized_view_pre_encoded.json--pre-encoded

Authorized view resource - Cloud Bigtable authorized view to create. Thearguments 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 inother ways.

To set theproject attribute:

• provide the argumentauthorized_view on the command line with afully specified name;
• provide the argument--project on the command line;
• set the propertycore/project.

This must be specified.

AUTHORIZED_VIEW

ID of the authorized-view or fully qualified identifier for the authorized-view.

To set theauthorized_view attribute:

• provide the argumentauthorized_view on the command line.

This positional argument must be specified if any of the other arguments in thisgroup are specified.

--instance=INSTANCE

Name of the Bigtable instance.

To set theinstance attribute:

• provide the argumentauthorized_view on the command line with afully specified name;
• provide the argument--instance on the command line.

--table=TABLE

Name of the Bigtable table.

To set thetable attribute:

• provide the argumentauthorized_view on the command line with afully specified name;
• provide the argument--table on the command line.

--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.

Thename field is ignored. The name is deduced from the othercommand line arguments.

Example: { "subsetView": { "rowPrefixes": ["store1#"], "familySubsets": {"column_family_name": { "qualifiers":["address"], "qualifierPrefixes":["tel"] }} }, "deletionProtection": true }

--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 andshould be used directly.

Run$gcloud help for details.