gcloud dataplex entry-groups add-iam-policy-binding

NAME
gcloud dataplex entry-groups add-iam-policy-binding - add IAM policy binding to a Dataplex Entry Group
SYNOPSIS
gcloud dataplex entry-groups add-iam-policy-binding (ENTRY_GROUP : --location=LOCATION) --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG …]
DESCRIPTION
Add IAM policy binding to a Dataplex Entry Group.
EXAMPLES
To add an IAM policy binding for the role of roles/dataplex.viewer for the user test-user@gmail.com to Entry Group test-entry-group in project test-project and in location us-central1, run: 
gcloud dataplex entry-groups add-iam-policy-binding test-entry-group --project=test-project --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
Entry group resource - Arguments and flags that define the Dataplex entry group you want to add IAM policy binding to. 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 entry_group 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.

ENTRY_GROUP
ID of the entry group or fully qualified identifier for the entry group.

To set the entry-group attribute:

  • provide the argument entry_group 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 entry_group 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 add 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.

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
Role name to assign to the principal. The role name is the complete path of a predefined role, such as roles/logging.viewer, or the role ID for a custom role, such as organizations/{ORGANIZATION_ID}/roles/logging.viewer.
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 variant is also available: 
gcloud alpha dataplex entry-groups add-iam-policy-binding