gcloud beta data-fusion add-iam-policy-binding

NAME
gcloud beta data-fusion add-iam-policy-binding - adds an IAM policy bindng to a Cloud Data Fusion instance
SYNOPSIS
gcloud beta data-fusion add-iam-policy-binding (INSTANCE : --location=LOCATION) --member=PRINCIPAL --role=ROLE [--namespace=NAMESPACE] [GCLOUD_WIDE_FLAG]
EXAMPLES
To set someone@example.com to have roles/datafusion.admin permission for instance my-instance, in project my-project, location in my-location, run:
gcloud beta data-fusion add-iam-policy-binding my-instance --location=my-location --member=user:someone@example.com --role=roles/datafusion.admin

To run the same command for a specific namespace on the instance, run:

gcloud beta data-fusion add-iam-policy-binding my-instance --location=my-location --member=user:someone@example.com --role=roles/datafusion.admin --namespace=my-namespace
POSITIONAL ARGUMENTS
Instance resource - Instance to add IAM 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 instance 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.

INSTANCE
ID of the instance or fully qualified identifier for the instance.

To set the instance attribute:

  • provide the argument instance on the command line.

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

--location=LOCATION
Compute Engine region in which to create the instance.

To set the location attribute:

  • provide the argument instance on the command line with a fully specified name;
  • provide the argument --location on the command line;
  • set the property datafusion/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.
OPTIONAL FLAGS
--namespace=NAMESPACE
CDAP Namespace whose IAM policy we wish to append. For example: --namespace=my-namespace.
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 beta and might change without notice.