gcloud spanner backup-schedules remove-iam-policy-binding

NAME
gcloud spanner backup-schedules remove-iam-policy-binding - remove IAM policy binding of a Cloud Spanner backup schedule
SYNOPSIS
gcloud spanner backup-schedules remove-iam-policy-binding(BACKUP_SCHEDULE :--database=DATABASE--instance=INSTANCE)--member=PRINCIPAL--role=ROLE[--all    |--condition=[KEY=VALUE,…]    |--condition-from-file=PATH_TO_FILE][GCLOUD_WIDE_FLAG]
DESCRIPTION
Remove an IAM policy binding of a Cloud Spanner backup schedule. One bindingconsists of a member, a role, and an optional condition.
EXAMPLES
To remove an IAM policy binding for the role of 'roles/editor' for the user'test-user@gmail.com', run:
gcloudspannerbackup-schedulesremove-iam-policy-bindingbackup-schedule-id--instance=instance-id--database=database-id--member='user:test-user@gmail.com'--role='roles/editor'

To remove an IAM policy binding which expires at the end of the year 2025 forthe role of 'roles/editor' and the user 'test-user@gmail.com', run:

gcloudspannerbackup-schedulesremove-iam-policy-bindingbackup-schedule-id--instance=instance-id--database=database-id--member='user:test-user@gmail.com'--role='roles/editor'--condition='expression=request.time< timestamp("2026-01-01T00:00:00Z"),title=expires_end_of_2025,descrip\tion=Expires at midnight on 2025-12-31'

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

POSITIONAL ARGUMENTS
BackupSchedule resource - The Cloud Spanner backup schedule to remove the IAMpolicy binding from. The arguments in this group can be used to specify theattributes of this resource. (NOTE) Some attributes are not given arguments inthis group but can be set in other ways.

To set theproject attribute:

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

This must be specified.

BACKUP_SCHEDULE
ID of the backupSchedule or fully qualified identifier for the backupSchedule.

To set thebackup_schedule attribute:

  • provide the argumentbackup_schedule on the command line.

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

--database=DATABASE
The name of the Cloud Spanner database.To set thedatabase attribute:
  • provide the argumentbackup_schedule on the command line with afully specified name;
  • provide the argument--database on the command line.
--instance=INSTANCE
The name of the Cloud Spanner instance.To set theinstance attribute:
  • provide the argumentbackup_schedule on the command line with afully specified name;
  • provide the argument--instance on the command line;
  • set the propertyspanner/instance.
REQUIRED FLAGS
--member=PRINCIPAL
The principal to remove 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.

Deleted principals have an additionaldeleted: prefix and a?uid=UID suffix, whereUID isa unique identifier for the principal. Example:deleted:user:test-user@gmail.com?uid=123456789012345678901.

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
The role to remove the principal from.
OPTIONAL FLAGS
At most one of these can be specified:
--all
Remove all bindings with this role and principal, irrespective of anyconditions.
--condition=[KEY=VALUE,…]
The condition of the binding that you want to remove. When the condition isexplicitly specified asNone (--condition=None), abinding without a condition is removed. Otherwise, only a binding with acondition that exactly matches the specified condition (including the optionaldescription) is removed. 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 thespanner/v1 API. The full documentation forthis API can be found at:https://cloud.google.com/spanner/
NOTES
These variants are also available:
gcloudalphaspannerbackup-schedulesremove-iam-policy-binding
gcloudbetaspannerbackup-schedulesremove-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-05-07 UTC.