gcloud beta bigtable backups add-iam-policy-binding

NAME
gcloud beta bigtable backups add-iam-policy-binding - add an IAM policy binding to a Cloud Bigtable Backup
SYNOPSIS
gcloud beta bigtable backups add-iam-policy-binding(BACKUP :--cluster=CLUSTER--instance=INSTANCE)--member=PRINCIPAL--role=ROLE[--condition=[KEY=VALUE,…]    |--condition-from-file=PATH_TO_FILE][GCLOUD_WIDE_FLAG]
DESCRIPTION
(BETA) Add an IAM policy binding to a Cloud Bigtable Backup. Onebinding consists of a member, a role, and an optional condition.
EXAMPLES
To add an IAM policy binding for the role ofroles/editor for theusertest-user@gmail.com with backupmy-backup ininstancemy-instance and clustermy-cluster, run:
gcloudbetabigtablebackupsadd-iam-policy-bindingmy-backup--instance=`my-instance`--cluster=`my-cluster`--member=`user:test-user@gmail.com`--role=`roles/editor`

To add an IAM policy binding which expires at the end of the year 2020 for therole ofroles/bigtable.admin and the usertest-user@gmail.com with backupmy-backup in instancemy-instance and clustermy-cluster, run:

gcloudbetabigtablebackupsadd-iam-policy-bindingmy-backup--instance=`my-instance`--cluster=`my-cluster`--member=`user:test-user@gmail.com`--role=`roles/bigtable.admin`--condition=`expression=request.time <timestamp("2021-01-01T00:00:00Z"),title=expires_end_of_2020,description=Expiresatmidnighton2020-12-31`

Seehttps://cloud.google.com/iam/docs/managing-policiesfor details of policy role and member types.

POSITIONAL ARGUMENTS
Backup resource - Cloud Bigtable Backup to add the IAM policy binding to. 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 argumentbackup on the command line with a fullyspecified name;
  • provide the argument--project on the command line;
  • set the propertycore/project.

This must be specified.

BACKUP
ID of the backup or fully qualified identifier for the backup.

To set thebackup attribute:

  • provide the argumentbackup on the command line.

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

--cluster=CLUSTER
Name of the Bigtable cluster.

To set thecluster attribute:

  • provide the argumentbackup on the command line with a fullyspecified name;
  • provide the argument--cluster on the command line.
--instance=INSTANCE
Name of the Bigtable instance.

To set theinstance attribute:

  • provide the argumentbackup on the command line with a fullyspecified name;
  • provide the argument--instance on the command line.
REQUIRED FLAGS
--member=PRINCIPAL
The principal to add the binding for. Should be of the formuser|group|serviceAccount:email ordomain:domain.

Examples:user:test-user@gmail.com,group:admins@example.com,serviceAccount:test123@example.domain.com, ordomain:example.domain.com.

Some resources also accept the following special values:

  • allUsers - Special identifier that represents anyone who is on theinternet, with or without a Google account.
  • allAuthenticatedUsers - Special identifier that represents anyonewho is authenticated with a Google account or a service account.
--role=ROLE
Role name to assign to the principal. The role name is the complete path of apredefined role, such asroles/logging.viewer, or the role ID for acustom role, such asorganizations/{ORGANIZATION_ID}/roles/logging.viewer.
OPTIONAL FLAGS
At most one of these can be specified:
--condition=[KEY=VALUE,…]
A condition to include in the binding. When the condition is explicitlyspecified asNone (--condition=None), a bindingwithout a condition is added. When the condition is specified and is notNone,--role cannot be a basic role. Basic roles areroles/editor,roles/owner, androles/viewer. For more on conditions, refer to the conditionsoverview guide:https://cloud.google.com/iam/docs/conditions-overview

When using the--condition flag, include the following key-valuepairs:

expression
(Required) Condition expression that evaluates to True or False. This uses asubset of Common Expression Language syntax.

If the condition expression includes a comma, use a different delimiter toseparate the key-value pairs. Specify the delimiter before listing the key-valuepairs. For example, to specify a colon (:) as the delimiter, do thefollowing:--condition=^:^title=TITLE:expression=EXPRESSION. Formore information, seehttps://cloud.google.com/sdk/gcloud/reference/topic/escaping.

title
(Required) A short string describing the purpose of the expression.
description
(Optional) Additional description for the expression.
--condition-from-file=PATH_TO_FILE
Path to a local JSON or YAML file that defines the condition. To see availablefields, see the help for--condition. Use a full or relative pathto a local file containing the value of condition.
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 thebigtableadmin/v2 API. The full documentationfor this API can be found at:https://cloud.google.com/bigtable/
NOTES
This command is currently in beta and might change without notice. Thesevariants are also available:
gcloudbigtablebackupsadd-iam-policy-binding
gcloudalphabigtablebackupsadd-iam-policy-binding

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-07-15 UTC.