gcloud beta kms ekm-config remove-iam-policy-binding - remove IAM policy binding from an EkmConfig

gcloud beta kms ekm-config remove-iam-policy-binding--location=LOCATION--member=PRINCIPAL--role=ROLE[--all    |--condition=[KEY=VALUE,…]    |--condition-from-file=PATH_TO_FILE][GCLOUD_WIDE_FLAG …]

gcloudbetakmsekm-configremove-iam-policy-binding--location='us-central1'--member='user:test-user@gmail.com'--role='roles/editor'

To remove an IAM policy binding with a condition of expression='request.time< timestamp("2023-01-01T00:00:00Z")', title='expires_end_of_2022', anddescription='Expires at midnight on 2022-12-31' for the role of 'roles/editor'for the user 'test-user@gmail.com' on the EkmConfig with location us-central1,run:

gcloudbetakmsekm-configremove-iam-policy-binding--location='us-central1'--member='user:test-user@gmail.com'--role='roles/editor'--condition='expression=request.time<timestamp("2023-01-01T00:00:00Z"),title=expires_end_of_2022,description=Expiresat midnight on 2022-12-31'

To remove all IAM policy bindings regardless of the condition for the role of'roles/editor' and for the user 'test-user@gmail.com' on the EkmConfig withlocation us-central1, run:

gcloudbetakmsekm-configremove-iam-policy-bindinglaplace--location='us-central1'--member='user:test-user@gmail.com'--role='roles/editor'--all

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

Location resource - The KMS location resource. This represents a Cloud resource.(NOTE) Some attributes are not given arguments in this group but can be set inother ways.

To set theproject attribute:

• provide the argument--location on the command line with a fullyspecified name;
• set the propertycore/project.

This must be specified.

--location=LOCATION

ID of the location or fully qualified identifier for the location.

To set thelocation attribute:

• provide the argument--location on the command line.

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

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.

Run$gcloud help for details.