gcloud alpha metastore services databases set-iam-policy - set the IAM policy for a database
gcloud alpha metastore services databases set-iam-policy (DATABASE : --location=LOCATION --service=SERVICE) POLICY_FILE [GCLOUD_WIDE_FLAG ...]
(ALPHA) Sets the IAM policy for the given database as defined in a JSON or YAML file.
See https://cloud.google.com/iam/docs/managing-policies for details of the policy file format and contents.
The following command will read an IAM policy defined in a JSON file 'policy.json' and set it for the database 'my-database':
$ gcloud alpha metastore services databases set-iam-policy \ my-database policy.json
- Database resource - Database for which to display the IAM policy. 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 database 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.
- DATABASE
ID of the database or fully qualified identifier for the database. To set the database attribute:
provide the argument database 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 database 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 database on the command line with a fully specified name;
provide the argument --service on the command line.
- POLICY_FILE
Path to a local JSON or YAML formatted file containing a valid policy.
The output of the get-iam-policy command is a valid file, as is any JSON or YAML file conforming to the structure of a Policy https://cloud.google.com/iam/reference/rest/v1/Policy.
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 uses the metastore/v1alpha API. The full documentation for this API can be found at: https://cloud.google.com/dataproc-metastore/docs
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 beta metastore services databases set-iam-policy