- 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-rolesUSERNAME--cluster=CLUSTER--db-roles=[ROLE,…]--region=REGION[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.
- 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 helpfor 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-rolesgcloud beta alloydb users set-roles
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-07-16 UTC.