mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-14 08:55:34 +00:00
57 lines
1.9 KiB
Text
57 lines
1.9 KiB
Text
NAME
|
|
gcloud alpha alloydb users set-roles - update an AlloyDB user's database
|
|
roles within a given cluster and region
|
|
|
|
SYNOPSIS
|
|
gcloud alpha alloydb users set-roles USERNAME --cluster=CLUSTER
|
|
--db-roles=[ROLE,...] --region=REGION
|
|
[--keep-extra-roles=KEEP_EXTRA_ROLES] [GCLOUD_WIDE_FLAG ...]
|
|
|
|
DESCRIPTION
|
|
(ALPHA) Update an AlloyDB user's database roles within a given cluster and
|
|
region.
|
|
|
|
EXAMPLES
|
|
To update a user's database roles, run:
|
|
|
|
$ gcloud alpha alloydb users set-roles my-username \
|
|
--cluster=my-cluster --region=us-central1 --db-roles=role1,role2
|
|
|
|
POSITIONAL ARGUMENTS
|
|
USERNAME
|
|
AlloyDB username
|
|
|
|
REQUIRED FLAGS
|
|
--cluster=CLUSTER
|
|
AlloyDB cluster ID
|
|
|
|
--db-roles=[ROLE,...]
|
|
Comma separated list of database roles this new user will be granted
|
|
upon creation.
|
|
|
|
--region=REGION
|
|
Regional location (e.g. asia-east1, us-east1). See the full list of
|
|
regions at https://cloud.google.com/sql/docs/instance-locations.
|
|
|
|
OPTIONAL FLAGS
|
|
--keep-extra-roles=KEEP_EXTRA_ROLES
|
|
If the user already exists and has extra roles, keep them.
|
|
|
|
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 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 alloydb users set-roles
|
|
|
|
$ gcloud beta alloydb users set-roles
|
|
|