
.TH "GCLOUD_ALLOYDB_USERS_SET\-SUPERUSER" 1



.SH "NAME"
.HP
gcloud alloydb users set\-superuser \- update an AlloyDB user's superuser role within a given cluster and region



.SH "SYNOPSIS"
.HP
\f5gcloud alloydb users set\-superuser\fR \fIUSERNAME\fR \fB\-\-cluster\fR=\fICLUSTER\fR \fB\-\-region\fR=\fIREGION\fR \fB\-\-superuser\fR=\fISUPERUSER\fR [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

Update an AlloyDB user's superuser role within a given cluster and region.



.SH "EXAMPLES"

To update a user's superuser role, run:

.RS 2m
$ gcloud alloydb users set\-superuser my\-username \e
    \-\-cluster=my\-cluster \-\-region=us\-central1 \-\-superuser=true/false
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m
\fIUSERNAME\fR

AlloyDB username


.RE
.sp

.SH "REQUIRED FLAGS"

.RS 2m
.TP 2m
\fB\-\-cluster\fR=\fICLUSTER\fR

AlloyDB cluster ID

.TP 2m
\fB\-\-region\fR=\fIREGION\fR

Regional location (e.g. \f5asia\-east1\fR, \f5us\-east1\fR). See the full list
of regions at https://cloud.google.com/sql/docs/instance\-locations.

.TP 2m
\fB\-\-superuser\fR=\fISUPERUSER\fR

If true, user will have AlloyDB superuser privileges


.RE
.sp

.SH "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 \fB$ gcloud help\fR for details.



.SH "NOTES"

These variants are also available:

.RS 2m
$ gcloud alpha alloydb users set\-superuser
.RE

.RS 2m
$ gcloud beta alloydb users set\-superuser
.RE


