gcloud alpha dataplex lakes remove-iam-policy-binding

NAME
gcloud alpha dataplex lakes remove-iam-policy-binding - remove IAM policy binding from a Dataplex lake resource
SYNOPSIS
gcloud alpha dataplex lakes remove-iam-policy-binding (LAKE : --location=LOCATION) --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG …]
DESCRIPTION
(ALPHA) Remove IAM policy binding from a Dataplex lake resource.
EXAMPLES
To remove an IAM policy binding for the role roles/dataplex.viewer for the user test-user@gmail.com from lake test-lake in location 'us-central', run: 
gcloud alpha dataplex lakes remove-iam-policy-binding test-lake --location=us-central1 --role=roles/dataplex.viewer --member=user:foo@gmail.com

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

POSITIONAL ARGUMENTS
Lakes resource - Arguments and flags that define the Dataplex lake you want to remove IAM policy binding from. The arguments 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 in other ways.

To set the project attribute:

  • provide the argument lake on the command line with a fully specified name;
  • provide the argument --project on the command line;
  • set the property core/project.

This must be specified.

LAKE
ID of the lakes or fully qualified identifier for the lakes.

To set the lake attribute:

  • provide the argument lake on the command line.

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

--location=LOCATION
The location of the Dataplex resource.

To set the location attribute:

  • provide the argument lake on the command line with a fully specified name;
  • provide the argument --location on the command line;
  • set the property dataplex/location.
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.
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. This variant is also available: 
gcloud dataplex lakes remove-iam-policy-binding