gcloud alpha data-catalog entry-groups add-iam-policy-binding

NAME
gcloud alpha data-catalog entry-groups add-iam-policy-binding - add an IAM policy binding to a Data Catalog entry group
SYNOPSIS
gcloud alpha data-catalog entry-groups add-iam-policy-binding (ENTRY_GROUP : --location=LOCATION) --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG]
DESCRIPTION
(ALPHA) Add an IAM policy binding to a Data Catalog entry group.
EXAMPLES
To add an IAM policy binding for the role of 'roles/editor' for the user 'test-user@gmail.com' with entry group 'group1' and location 'us-central1', run:
gcloud alpha data-catalog entry-groups add-iam-policy-binding group1 --location='us-central1' --member='user:test-user@gmail.com' --role='roles/editor'

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

POSITIONAL ARGUMENTS
Entry group resource - Entry group for which to add an IAM policy binding. 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
Location of the entry group. 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.
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.

API REFERENCE
This command uses the datacatalog/v1beta1 API. The full documentation for this API can be found at: https://cloud.google.com/data-catalog/docs/
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 data-catalog entry-groups add-iam-policy-binding
gcloud beta data-catalog entry-groups add-iam-policy-binding