gcloud alpha dataplex glossaries remove-iam-policy-binding

NAME
gcloud alpha dataplex glossaries remove-iam-policy-binding - removes IAM policy binding from a Dataplex Glossary
SYNOPSIS
gcloud alpha dataplex glossaries remove-iam-policy-binding(GLOSSARY :--location=LOCATION)--member=PRINCIPAL--role=ROLE[GCLOUD_WIDE_FLAG …]
DESCRIPTION
(ALPHA) Removes IAM policy binding from a Dataplex Glossary.
EXAMPLES
To remove an IAM policy binding for the roleroles/dataplex.viewerfor the usertest-user@gmail.com from a glossarytest-glossary within projettest-project in locationus-central1, run:
gcloudalphadataplexglossariesremove-iam-policy-bindingtest-glossary--project=test-project--location=us-central1--role=roles/dataplex.viewer--member=user:test-user@gmail.comSeehttps://cloud.google.com/dataplex/docs/iam-rolesfordetailsofpolicyroleandmembertypes.
POSITIONAL ARGUMENTS
Glossary resource - Arguments and flags that define the Dataplex Glossary youwant to remove IAM policy binding from The arguments in this group can be usedto specify the attributes of this resource. (NOTE) Some attributes are not givenarguments in this group but can be set in other ways.

To set theproject attribute:

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

This must be specified.

GLOSSARY
ID of the glossary or fully qualified identifier for the glossary.

To set theglossary attribute:

  • provide the argumentglossary on the command line.

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

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

To set thelocation attribute:

  • provide the argumentglossary on the command line with a fullyspecified name;
  • provide the argument--location on the command line;
  • set the propertydataplex/location.
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.
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 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. This variant is also available:
gclouddataplexglossariesremove-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-13 UTC.