NAME

gcloud alpha metastore services backups add-iam-policy-binding - add an IAM policy binding to a backup

SYNOPSIS

gcloud alpha metastore services backups add-iam-policy-binding (BACKUP : --location=LOCATION --service=SERVICE) --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...]

DESCRIPTION

(ALPHA) Add an IAM policy binding to a backup.

EXAMPLES

To add an IAM policy binding for the role of 'roles/metastore.admin' for the user 'test-user@gmail.com', run:

$ gcloud alpha metastore services backups add-iam-policy-binding \ my-backup --member='user:test-user@gmail.com' \ --role='roles/metastore.admin'

See https://cloud.google.com/dataproc-metastore/docs/iam-and-access-control for details of policy role and member types.

POSITIONAL ARGUMENTS

Backup resource - Backup for which to add the IAM policy 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 backup on the command line with a fully specified name;

set the property core/project;

provide the argument --project on the command line.

This must be specified.

BACKUP

ID of the backup or fully qualified identifier for the backup. To set the backup attribute:

  • provide the argument backup 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 Dataproc Metastore service.

If not specified, will use default metastore/location.

To set the location attribute:

  • provide the argument backup on the command line with a fully specified name;

  • provide the argument --location on the command line;

  • set the property metastore/location.

--service=SERVICE

The identifier of the Dataproc Metastore service To set the service attribute:

  • provide the argument backup on the command line with a fully specified name;

  • provide the argument --service 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 metastore/v1alpha API. The full documentation for this API can be found at: https://cloud.google.com/dataproc-metastore/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 metastore services backups add-iam-policy-binding

$ gcloud beta metastore services backups add-iam-policy-binding