gcloud alpha resource-manager tags keys remove-iam-policy-binding

NAME
gcloud alpha resource-manager tags keys remove-iam-policy-binding - removes a policy binding from the IAM policy of a TagKey
SYNOPSIS
gcloud alpha resource-manager tags keys remove-iam-policy-binding RESOURCE_NAME --member=PRINCIPAL --role=ROLE [--all     | --condition=[KEY=VALUE,…]     | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG]
DESCRIPTION
(ALPHA) Removes an IAM policy binding for a TagKey resource given the binding and an identifier for the TagKey. The identifier can be the TagKey's parent/short name or the TagKey's ID in the form: tagKeys/{numeric_id}.
EXAMPLES
To remove an IAM policy binding for the role of 'roles/editor' for the user 'test-user@gmail.com' on the tagKey 'tagKeys/123', run:
gcloud alpha resource-manager tags keys remove-iam-policy-binding tagKeys/123 --member='user:test-user@gmail.com' --role='roles/editor'

To remove an IAM policy binding for a TagKey with the name 'env' under 'organization/456' for the role of 'roles/resourcemanager.tagUser' for the user 'test-user@gmail.com', run:

gcloud alpha resource-manager tags keys remove-iam-policy-binding 456/env --member='user:test-user@gmail.com' --role='roles/resourcemanager.tagUser'

See https://cloud.google.com/iam/docs/managing-policies for details of policy role and member types.

POSITIONAL ARGUMENTS
RESOURCE_NAME
Resource name or namespaced name. The resource name should be in the form {resource_type}/{numeric_id}. The namespaced name should be in the form {org_id}/{short_name} where short_name must be 1-63 characters, beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with dashes (-), underscores ( _ ), dots (.), and alphanumerics between.
REQUIRED FLAGS
--member=PRINCIPAL
The principal to remove the binding for. Should be of the form user|group|serviceAccount:email or domain:domain.

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

Deleted principals have an additional deleted: prefix and a ?uid=UID suffix, where UID is a 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 the internet, with or without a Google account.
  • allAuthenticatedUsers - Special identifier that represents anyone who 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 any conditions.
--condition=[KEY=VALUE,…]
The condition of the binding that you want to remove. When the condition is explicitly specified as None (--condition=None), a binding without a condition is removed. Otherwise, only a binding with a condition that exactly matches the specified condition (including the optional description) is removed. For more on conditions, refer to the conditions overview guide: https://cloud.google.com/iam/docs/conditions-overview

When using the --condition flag, include the following key-value pairs:

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

If the condition expression includes a comma, use a different delimiter to separate the key-value pairs. Specify the delimiter before listing the key-value pairs. For example, to specify a colon (:) as the delimiter, do the following: --condition=^:^title=TITLE:expression=EXPRESSION. For more information, see https://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=CONDITION_FROM_FILE
Path to a local JSON or YAML file that defines the condition. To see available fields, see the help for --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.

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 resource-manager tags keys remove-iam-policy-binding
gcloud beta resource-manager tags keys remove-iam-policy-binding