gcloud alpha dataplex content add-iam-policy-binding - adds IAM policy binding to a Dataplex Content
gcloud alpha dataplex content add-iam-policy-binding (CONTENT : --lake=LAKE --location=LOCATION) --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...]
(ALPHA) Adds IAM policy binding to a Dataplex Content.
To add an IAM policy binding for the role of roles/dataplex.viewer for the user 'testuser@gmail.com' to content test-content within lake test-lake in location us-central, run:
$ gcloud alpha dataplex content add-iam-policy-binding \ test-content --project=test-project --location=us-central1 \ --lake=test-lake --role=roles/dataplex.viewer \ --member=user:testuser@gmail.com
See https://cloud.google.com/dataplex/docs/iam-roles for details of policy role and member types.
- Content resource - The Content 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 content 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.
- CONTENT
ID of the content or fully qualified identifier for the content. To set the content attribute:
provide the argument content on the command line.
This positional argument must be specified if any of the other arguments in this group are specified.
- --lake=LAKE
The identifier of the Dataplex lake resource. To set the lake attribute:
provide the argument content on the command line with a fully specified name;
provide the argument --lake on the command line.
- --location=LOCATION
The location of the Dataplex resource. To set the location attribute:
provide the argument content on the command line with a fully specified name;
provide the argument --location on the command line;
set the property dataplex/location.
- --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.
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.
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 content add-iam-policy-binding