gcloud alpha iap tcp dest-groups remove-iam-policy-binding Stay organized with collections Save and categorize content based on your preferences.
- NAME
- gcloud alpha iap tcp dest-groups remove-iam-policy-binding - remove IAM policy binding from an IAP TCP Destination Group resource
- SYNOPSIS
gcloud alpha iap tcp dest-groups remove-iam-policy-binding--dest-group=DEST_GROUP--member=PRINCIPAL--region=REGION--role=ROLE[--all|--condition=[KEY=VALUE,…] |--condition-from-file=PATH_TO_FILE][GCLOUD_WIDE_FLAG …]
- DESCRIPTION
(ALPHA)Removes a policy binding from the IAM policy of an IAP TCPDestination Group resource. One binding consists of a member, a role and anoptional condition.- EXAMPLES
- To remove an IAM policy binding for the role of'roles/iap.tunnelResourceAccessor' for the user 'test-user@gmail.com' in thegroup 'my-group' located in the region 'us-west1', run:
gcloudalphaiaptcpdest-groupsremove-iam-policy-binding--member='user:test-user@gmail.com'--role='roles/iap.tunnelResourceAccessor'--dest-group='my-group'--region='us-west1'To remove an IAM policy binding for the role of'roles/iap.tunnelResourceAccessor' from all authenticated users in the group'my-group' located in the region 'us-west1', run:
gcloudalphaiaptcpdest-groupsremove-iam-policy-binding--member='allAuthenticatedUsers'--role='roles/iap.tunnelResourceAccessor'--dest-group='my-group'--region='us-west1'To remove an IAM policy binding which expires at the end of the year 2018 forthe role of 'roles/iap.tunnelResourceAccessor' for the user'test-user@gmail.com' in the group 'my-group' located in the region 'us-west1',run:
gcloudalphaiaptcpdest-groupsremove-iam-policy-binding--member='user:test-user@gmail.com'--role='roles/iap.tunnelResourceAccessor'--condition='expression=request.time<timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018, description=Expires at midnight on 2018-12-31'\--dest-group='my-group'--region='us-west1'To remove all IAM policy bindings regardless of the condition for the role of'roles/iap.tunnelResourceAccessor' and for the user 'test-user@gmail.com' in thegroup 'my-group' located in the region 'us-west1', run:
gcloudalphaiaptcpdest-groupsremove-iam-policy-binding--member='user:test-user@gmail.com'--role='roles/iap.tunnelResourceAccessor'--dest-group='my-group'--region='us-west1'Seehttps://cloud.google.com/iam/docs/managing-policiesfor details of policy role and member types.
- REQUIRED FLAGS
--dest-group=DEST_GROUP- Name of the Destination Group.
--member=PRINCIPAL- The principal to remove the binding for. Should be of the form
user|group|serviceAccount:emailordomain:domain.Examples:
user:test-user@gmail.com,group:admins@example.com,serviceAccount:test123@example.domain.com, ordomain:example.domain.com.Deleted principals have an additional
deleted:prefix and a?uid=UIDsuffix, whereisa unique identifier for the principal. Example:UIDdeleted: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.
--region=REGION- Region of the Destination Group.
--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 as
None(--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-overviewWhen using the
--conditionflag, 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.
- At most one of these can be specified:
- 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 helpfor details. - NOTES
- This command is currently in alpha and might change without notice. If thiscommand fails with API permission errors despite specifying the correct project,you might be trying to access an API with an invitation-only early accessallowlist. These variants are also available:
gcloudiaptcpdest-groupsremove-iam-policy-bindinggcloudbetaiaptcpdest-groupsremove-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.